[SERVER-64444] listIndexes fails on invalid pre-5.0 index spec after upgrade Created: 11/Mar/22 Updated: 23/Jan/24 Resolved: 15/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.0.4 |
| Fix Version/s: | 6.1.0-rc0, 5.0.25, 6.0.14 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Yuhong Zhang |
| 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, v5.3, v5.0
|
||||||||||||||||||||||||||||
| Sprint: | Execution Team 2022-04-18, Execution Team 2022-05-02 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||||||
| Description |
|
Invalid index options, such as specifying "sparse" as a string rather than a boolean, may have been created in the past, before the createIndexes command started validating options more strictly. In MongoDB 5.0, the listIndexes command more strictly validates index options, and fails when an invalid option is encountered. At this point, the only option is to drop and recreate the index. This is a variation on the problem addressed in |
| Comments |
| Comment by Githook User [ 23/Jan/24 ] |
|
Author: {'name': 'Yuhong Zhang', 'email': 'yuhong.zhang@mongodb.com', 'username': 'YuhongZhang98'}Message: (cherry picked from commit 248c9c2f35e0a0b1fcf1e56c35ed2fb06682cd14) GitOrigin-RevId: 7d10c32c6dbbf401a961679c52b0b4bc69e53f52 |
| Comment by Githook User [ 23/Jan/24 ] |
|
Author: {'name': 'Yuhong Zhang', 'email': 'yuhong.zhang@mongodb.com', 'username': 'YuhongZhang98'}Message: (cherry picked from commit 9b6755d018fa749405cc2a603c1c5d935a20a742) GitOrigin-RevId: 23f3691e54c5cad037841ad1a4cdb6653a1af2fa |
| Comment by Githook User [ 22/Jan/24 ] |
|
Author: {'name': 'Yuhong Zhang', 'email': 'yuhong.zhang@mongodb.com', 'username': 'YuhongZhang98'}Message: (cherry picked from commit 248c9c2f35e0a0b1fcf1e56c35ed2fb06682cd14) GitOrigin-RevId: b9046a28ab1f3c620b139399d0d112aa03a1eba3 |
| Comment by Githook User [ 22/Jan/24 ] |
|
Author: {'name': 'Yuhong Zhang', 'email': 'yuhong.zhang@mongodb.com', 'username': 'YuhongZhang98'}Message: (cherry picked from commit 9b6755d018fa749405cc2a603c1c5d935a20a742) GitOrigin-RevId: d8c557be9b692881a2ef796680c54936c647256a |
| Comment by Githook User [ 10/Oct/22 ] |
|
Author: {'name': 'Yuhong Zhang', 'email': 'yuhong.zhang@mongodb.com', 'username': 'YuhongZhang98'}Message: (cherry-picked from commit a59e32ba3883e46077a750d1f65f383e35ab3e12) |
| Comment by Githook User [ 10/Sep/22 ] |
|
Author: {'name': 'Yuhong Zhang', 'email': 'yuhong.zhang@mongodb.com', 'username': 'YuhongZhang98'}Message: (cherry-picked from commit a59e32ba3883e46077a750d1f65f383e35ab3e12) |
| Comment by Githook User [ 15/Apr/22 ] |
|
Author: {'name': 'Yuhong Zhang', 'email': 'yuhong.zhang@mongodb.com', 'username': 'YuhongZhang98'}Message: |
| Comment by Githook User [ 15/Apr/22 ] |
|
Author: {'name': 'Yuhong Zhang', 'email': 'yuhong.zhang@mongodb.com', 'username': 'YuhongZhang98'}Message: |
| Comment by Githook User [ 15/Apr/22 ] |
|
Author: {'name': 'Yuhong Zhang', 'email': 'yuhong.zhang@mongodb.com', 'username': 'YuhongZhang98'}Message: |
| Comment by Benety Goh [ 11/Mar/22 ] |
|
The validation and corrective action in Couple of possible resolutions:
|