-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
Execution Team 2022-01-24
Instead of supporting implicit collection creation (which is risky in any scenario) createIndex on an existing collection's cluster key with 'clustered' = true should be a no-op. Otherwise, throw if the collection does not already exist or already exists as clustered.
- related to
-
SERVER-85334 createClusteredInfoForNewCollection can be deleted
- Closed