You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Within the RecordQueryPlanner, the AndWithThenPlanner does not handle OneOfThemWithComponents. In practice, this means that if you had a record type like:
However, because the AndWithThenPlanner ignores OneOfThemWithComponents, this will get planned some other way (for example, using a less efficient index or scanning the record store).
The text was updated successfully, but these errors were encountered:
…WithComponent expressions
This adds support to the old planner to address a shortcoming where certain queries were choosing to use less efficient indexes due to a shortcoming with the `AndWithThenPlanner`. Based on the tests in the `NestedFieldQueryTest`, it looks like the new planner was already matching such expressions in this case, and so this shortcoming should only be in the old planner.
This fixesFoundationDB#1876.
…WithComponent expressions
This adds support to the old planner to address a shortcoming where certain queries were choosing to use less efficient indexes due to a shortcoming with the `AndWithThenPlanner`. Based on the tests in the `NestedFieldQueryTest`, it looks like the new planner was already matching such expressions in this case, and so this shortcoming should only be in the old planner.
This fixesFoundationDB#1876.
alecgrieser
added a commit
to alecgrieser/fdb-record-layer
that referenced
this issue
Oct 31, 2022
…WithComponent expressions
This adds support to the old planner to address a shortcoming where certain queries were choosing to use less efficient indexes due to a shortcoming with the `AndWithThenPlanner`. Based on the tests in the `NestedFieldQueryTest`, it looks like the new planner was already matching such expressions in this case, and so this shortcoming should only be in the old planner.
This fixesFoundationDB#1876.
Within the
RecordQueryPlanner
, theAndWithThenPlanner
does not handleOneOfThemWithComponent
s. In practice, this means that if you had a record type like:And a value index with an expression like:
Then you'd expect that index to satisfy the following query:
However, because the
AndWithThenPlanner
ignoresOneOfThemWithComponent
s, this will get planned some other way (for example, using a less efficient index or scanning the record store).The text was updated successfully, but these errors were encountered: