Support regex queries with label+property indices

[colinbarry]

Queries using a label+property index now correctly return matching results when comparing properties against regular expressions.

The problem was caused by index code rejecting ranges across different PropertyTypes as being invalid. This is true in most cases, (e.g. WHERE node.a > 'hello' AND node.a < 42) but not in the case where the upper-bound is an exclusive (<) bound on the next (from an ordering standpoint) PropertyType. As the exclusive upper bound exclusive sentinel is not compared against, it means that the range is still across a single PropertyType.

Regexes uses a range that is inclusively lower bounded on the empty string, and exclusively upper bounded on the minimum value of whatever PropertyType happens to follow string.

(This bug was a regression introduced by composite indices.)

#Fixes 3010

[colinbarry]

Tracking

• [Link to Epic/Issue]

Standard development

• Update unit/E2E tests
• Compare the benchmarking results between the master branch this branch

CI Testing Labels

• Select the appropriate CI test labels (CI -build=build-name -test=test-suite)

Documentation checklist

• Add the documentation label
• Add the bug / feature label
• Add the milestone for which this feature is intended
  • If not known, set for a later milestone
• Write a release note, including added/changed clauses
  • Queries using regex clauses on label+property indices no longer return an empty results set. Users can now use label+property indices to improve performance of regex queries (although note that, unlike exact text match queries, regex queries require an additional filtering step.) #3025

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud