Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
Fully Compatible
-
ALL
-
v6.1, v6.0, v5.0, v4.4
-
Sharding EMEA 2022-10-31, Sharding EMEA 2022-11-14
-
135
-
3
Description
A hidden index helps users evaluate the potential impact of dropping an index without actually dropping the index. That way, the user can just unhide the index if the impact is bad. Hidden and dropped indexes should therefore have the same behavior.
For sharding, however, we allow a shard key index that cannot be dropped to be hidden. In order to maintain consistency, we should not allow users to hide a shard key index that cannot be dropped.
Attachments
Issue Links
- causes
-
SERVER-74841 collMod should not call catalogClient::getCollection during secondary replication
-
- Closed
-
- is documented by
-
DOCS-15731 [Server] Investigate changes in SERVER-68769: If a shard key index cannot be dropped then a user should not be able to hide that index
-
- Closed
-
- related to
-
SERVER-67071 Sharding should not use hidden indexes
-
- Closed
-
-
SERVER-74841 collMod should not call catalogClient::getCollection during secondary replication
-
- Closed
-