[SERVER-63582] Fail gracefully if a user tries converting a unique index with old format keys to a non-unique index. Created: 11/Feb/22 Updated: 29/Oct/23 Resolved: 11/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Pavithra Vetriselvan | Assignee: | Benety Goh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Execution Team 2022-03-21 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
If a unique index was built before 4.2 and then upgraded to a later major version, it can have mixed format keys. We have no way of ensuring that these indexes only contain new format keys so we should fail the collMod conversion if we detect this scenario. We can probably check for the internal data format introduced in |
| Comments |
| Comment by Githook User [ 11/Mar/22 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |
| Comment by Githook User [ 10/Mar/22 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |
| Comment by Githook User [ 10/Mar/22 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |