[SERVER-70349] [CQF] Be consistent with scan definition names for queries involving multiple collections Created: 07/Oct/22 Updated: 05/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Nicholas Zolnierz | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Optimization
|
| Participants: |
| Description |
|
The main collection scan definition includes an appended UUID, while other foreign collections do not. The reason for this is because during translation of $unionWith, for instance, we only have a Namespace object to lookup the corresponding scan definition. We could either move to (1) just use the namespace or (2) lookup the UUID by namespace in the union/lookup translation. |