-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Execution Team 2021-11-01, Execution Team 2021-11-15
-
15
During tenant migration, it's possible for the tenant migration cloner to try and put the output for the clustered index into the _readyIndexSpecs for processing.
We should instead check if the field 'clustered' exists and if so, not append the spec to the _readyIndexSpecs
- depends on
-
SERVER-61009 Make createIndex a no-op on a cluster key if the collection exists
- Closed