Loading...

XML

Word

Printable

JSON

Details

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 6.1.1, 6.0.4, 6.2.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- shardingemea-qw

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v6.1, v6.0, v5.0, v4.4
Sprint:
Sharding EMEA 2022-10-31, Sharding EMEA 2022-11-14
Linked BF Score:
135
Story Points:
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

Activity

People

Assignee:: Pol Pinol

Reporter:: Garaudy Etienne

Participants:: Garaudy Etienne, Githook User, Pol Pinol, Tommaso Tocci

Votes:: 0 Vote for this issue

Watchers:: 7 Start watching this issue

Dates

Created:: Aug 12 2022 02:50:57 AM UTC

Updated:: Oct 29 2023 09:34:35 PM UTC

Resolved:: Nov 11 2022 12:27:10 PM UTC