-
Type:
Bug
-
Resolution: Cannot Reproduce
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Optimization
-
ALL
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Assigning a let variable in a $lookup to a numeric field path appears to set this variable to an incorrect value (see repro steps below).
- is related to
-
SERVER-36681 Dotted path {$ne: null} against array of scalars returns incorrect results
-
- In Code Review
-
-
SERVER-117479 Multiple $match stages in subpipeline prevent join optimization
-
- Closed
-