[SERVER-60979] TenantCollectionCloner::listIndexesStage() should filter out clustered indexes Created: 25/Oct/21 Updated: 01/Nov/21 Resolved: 01/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Haley Connelly |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | PM-2311-M1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Execution Team 2021-11-01, Execution Team 2021-11-15 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 15 | ||||||||
| Description |
|
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 |
| Comments |
| Comment by Haley Connelly [ 01/Nov/21 ] |
|
This feature will be tested inĀ |