-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We should be able to reorder joins arbitrarily, but preserve the semantics of seeing as fields operating on the same path prefix in the order in which they were written.
What we can do here is output such conflicting fields at the top-level of the final document, then reshape the document at the end.
- related to
-
SERVER-119240 HashJoin stage followed by a project gives incorrect result with join ordering enabled
-
- Closed
-
-
SERVER-113227 Add logic to bail out for join-reordering for conflicting "as" fields
-
- In Code Review
-