[SERVER-13116] distinct isn't sharding aware Created: 10/Mar/14  Updated: 24/Jul/23

Status: Backlog
Project: Core Server
Component/s: Querying, Sharding
Affects Version/s: 2.6.0-rc1
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: Mathias Stearn Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 2
Labels: query-44-grooming
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-3645 Sharded collection counts (on primary... Closed
is related to SERVER-42160 $group stages that use a DISTINCT_SCA... Backlog
Assigned Teams:
Query Optimization
Operating System: ALL
Participants:

 Description   

I think it needs to both set QueryPlannerParams::INCLUDE_SHARD_FILTER and either use a ClientCursor or a RangePreserver.



 Comments   
Comment by Ian Boros [ 07/Mar/18 ]

Moving back to Needs Triage at the suggestion of charlie.swanson. The fix may be similar to that for SERVER-3645, which is in-progress.

Comment by Mathias Stearn [ 10/Mar/14 ]

Removing count from this ticket since it is covered by SERVER-3645. Also bumping out of 2.6 since it isn't a regression and it seems like it should be in the same release-slot as SERVER-3645.

Generated at Thu Feb 08 03:30:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.