[SERVER-66910] Missing collection hides collection UUID mismatch for collMod unique index conversion Created: 31/May/22 Updated: 29/Oct/23 Resolved: 02/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc9, 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Noma |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v6.0
|
||||
| Sprint: | Execution Team 2022-06-13 | ||||
| Participants: | |||||
| Description |
|
When using collMod to convert an index to unique, we fail early here if the collection specified in the command does not exist. However, this causes us to not perform a collection UUID check even if the collectionUUID parameter was also specified. Note that this is only an issue on replica sets; on sharded clusters, the collectionUUID parameter is already honored even in this case. |
| Comments |
| Comment by Githook User [ 02/Jun/22 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: (cherry picked from commit 7768b6946b1c14139ed592b1612b3b421fe55e30) |
| Comment by Githook User [ 02/Jun/22 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |