[SERVER-62823] Return IndexAlreadyExists for clustered index in IndexCatalogImpl validation Created: 20/Jan/22 Updated: 29/Oct/23 Resolved: 21/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Haley Connelly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2022-01-24, Execution Team 2022-02-07 |
| Participants: |
| Description |
|
Right now, there are several places in the code that check whether an index with "clustered" is valid (here and here). By the time we get to _doesSpecClonflictWithExisting, _isSpecOK should already have confirmed a spec with "clustered" is valid with the collection specifications (and thus the clustered index specifications if the collection is clustered)
Additionally, IndexCatalogImpl::_doesSpecConflictWithExisting expects IndexAlreadyExists to be returned for indexes that already exist. Make this consistent for a clustered index |
| Comments |
| Comment by Githook User [ 21/Jan/22 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: |