implicitlyCreateIndex defaults to true and when set to false, will not create new indexes while running the shardCollection command.
enforceUniquenessCheck defaults to true and when set to false, ignores uniqueness property when validating indexes for shardCollection.
Regardless of both settings, shardCollection should still return an error if there are no index that is compatible with the new shard key pattern.
- causes
-
SERVER-64519 Critical section reason for create collection is multiversion incompatible
- Closed
-
SERVER-64580 Step downs while sharding a collection in mixed binaries shards might crash the old binary
- Closed
- related to
-
SERVER-64573 Make implicitlyCreateIndex and enforceUniquenessCheck fields optional
- Closed
-
SERVER-64142 Add new enforceUniqueness to refineCollectionShardKey command
- Closed