-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
v4.2
-
Execution Team 2021-11-15
This should include making the necessary catalog changes, but does not encompass checking for duplicates. We should avoid bumping the data format version so that there aren't any upgrade/downgrade implications.
- is related to
-
MONGOSH-1250 [MONGOSH] Incomplete output from collMod operation
- Closed
- related to
-
SERVER-61182 [inMemory] collmod_convert_to_unique.js fails under in-memory storage engine
- Backlog
-
SERVER-61181 [ephemeralForTest] collmod_convert_to_unique.js fails under ephemeralForTest storage engine
- Closed
-
SERVER-61980 collMod does not consider unique option in no-op hidden parameter request processing
- Closed
-
SERVER-61224 Investigate retryability of collMod command in mongos
- Closed
-
SERVER-63582 Fail gracefully if a user tries converting a unique index with old format keys to a non-unique index.
- Closed
-
SERVER-69874 Document or possibly mitigate scenario where shards end up with different prepareUnique and unique index settings
- Closed