-
Type: Task
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
Cluster Scalability 2024-07-08, Cluster Scalability 2024-07-22, Cluster Scalability 2024-08-19, Cluster Scalability 2024-09-02, Cluster Scalability 2024-10-14, Cluster Scalability 2024-10-28
Make "readConcern" take in an optional "$_skipShardFiltering" boolean field. When "$_skipShardFiltering" is true, the read should skip orphan docs filtering regardless of which readConcern it uses. The difference between readConcern "available" and readConcern with "$_skipShardFiltering": true is that the former makes the read skip both shard version check and shard filtering, whereas the latter makes the read skip only shard filtering.
This functionality is needed by SERVER-91030.
- is depended on by
-
SERVER-91030 analyzeShardKey against sharded collections may fail to find sampled docs if there has been data movement
- Closed
- related to
-
SERVER-92195 Consider making analyzeShardKey in 8.0.1+ only run cluster aggregate command for calculating cardinality and frequency metrics with readConcern "available" if the collection is sharded
- Closed