-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
When converting to SargableNode, when we encounter a Traverse with more than one requirement, retain original predicate, and retain one of the requirements as optional.
This will allow us to extract interval for elemMatch with nested fields.
- depends on
-
SERVER-69025 [CQF] Performance-only partial schema requirements
- Closed
- duplicates
-
SERVER-68596 [CQF] A SargableNode should be generated for an $elemMatch on a complex path
- Closed