-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
QO 2022-09-05, QO 2022-09-19, QO 2022-10-03
Allow a partial schema requirement to be marked as perf-only/optional. It will only be incorporated as part of index bounds, and never a residual predicate.
This will allow us to express extra predicates to satisfy yielding/transactional semantics: if we have a predicate which does not bind going on the left, it goes on the right as well, and the left side is marked as optional. It will also allow to model nested elemMatch, and array bounds (if we have an array constant as bound, we create a new bound using the first array element).
- is depended on by
-
SERVER-68596 [CQF] A SargableNode should be generated for an $elemMatch on a complex path
- Closed
-
SERVER-69024 [CQF] Handling of traverse with more than one partial schema requirement
- Closed
- is related to
-
SERVER-64007 Makes plans produced by Cascades optimizer yield
- Closed