[SERVER-31263] distinct command should pass routingInfo to scatterGather() Created: 26/Sep/17 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.13 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | gm-ack | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Query Optimization
|
||||
| Participants: | |||||
| Description |
|
The distinct command orders results according to the collection's default collation if the collection is sharded. It obtains the collection's default collation from the routingInfo. However, since scatterGather() internally gets its own copy of routingInfo, the routingInfo used in the command can be for a previous incarnation of the collection (and so have the wrong collection default collation). This ticket should make the versioned scatterGather() methods optionally take the routingInfo to use, for commands that need to use the routingInfo themselves for non-routing purposes. |
| Comments |
| Comment by Gregory McKeon (Inactive) [ 02/Mar/18 ] |
|
When the distinct command is removed, this goes away in master. |
| Comment by Gregory McKeon (Inactive) [ 23/Feb/18 ] |
|
Given that the distinct command is going to be deprecated, we're passing this to query to triage if this is necessary to fix. |