-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Sharding NYC
-
Fully Compatible
-
Sharding NYC 2023-03-06, Sharding NYC 2023-03-20, Sharding NYC 2023-04-03, Sharding NYC 2023-04-17
-
None
-
None
-
None
-
None
-
None
-
None
-
None
From the design:
mostCommonValues: [
// Top 5 most common shard key values. To avoid exceeding the 16MB
// limit for the response, the values would be truncated if they
// exceed a certain size.
{value: <shardkey>, frequency: <integer>},
...
]
- depends on
-
SERVER-72814 Support looking up original values from hash values
-
- Closed
-
- related to
-
SERVER-75886 Make analyzeShardKey command return shard key values correctly when the supporting index is hashed
-
- Closed
-
-
SERVER-75887 Complete TODO listed in SERVER-70994
-
- Closed
-