-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Sharding NYC
-
Fully Compatible
-
v7.0, v6.0, v5.0
-
Sharding NYC 2023-07-10, Sharding NYC 2023-07-24, Sharding NYC 2023-08-07
-
160
-
2
The hashed index is only needed to support chunk migrations. However, it hurts write performance. Most collections with hashed shard keys have even data distribution and growth, thus not requiring chunk migrations. As such, we should allow customers to drop the hashed index for hashed shard keys.
- is depended on by
-
SERVER-78995 Allow users to hide the last compatible hashed shard key index
- Closed
- related to
-
SERVER-78863 Audit places in the codebase that rely on the hashed index to ensure correct behavior.
- Closed
-
SERVER-78252 Block chunk migrations for hashed shard keys if you don’t have the shard key index
- Closed