[SERVER-36444] Ensure that "allPaths" indexes can be fully validated Created: 03/Aug/18 Updated: 29/Oct/23 Resolved: 19/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Bernard Gorman | Assignee: | James Wahlin |
| 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: | Query 2018-09-10, Query 2018-09-24 | ||||||||
| Participants: | |||||||||
| Description |
|
At present, allPaths indexes cannot be validated, both because their two-field keys do not align with the single-field $** keyPattern and because allPaths' multikey metadata keys are not considered by the current process. We should ensure that allPaths indexes can be fully validated, including both their data and metadata keys. |
| Comments |
| Comment by Githook User [ 19/Sep/18 ] |
|
Author: {'name': 'James Wahlin', 'email': 'james@mongodb.com', 'username': 'jameswahlin'}Message: Revert " This reverts commit 118cc1eeb978f9c5c8492368fe6b5a04669fe3c3. |
| Comment by Githook User [ 19/Sep/18 ] |
|
Author: {'name': 'James Wahlin', 'email': 'james@mongodb.com', 'username': 'jameswahlin'}Message: Additionally, don't fail validation on encountering multiple index |
| Comment by Githook User [ 19/Sep/18 ] |
|
Author: {'name': 'Ian Boros', 'email': 'ian.boros@10gen.com'}Message: |
| Comment by James Wahlin [ 12/Sep/18 ] |
|
This work will be done in 2 commits. The first (above) ignored $** multikey metadata paths when performing validation, and reenables validation in our tests. The second will add a mechanism to properly validate these entries. |
| Comment by Githook User [ 12/Sep/18 ] |
|
Author: {'name': 'James Wahlin', 'email': 'james@mongodb.com', 'username': 'jameswahlin'}Message: |