[SERVER-49937] Validate repair mode should fix up wildcard indexes without multikey metadata keys Created: 27/Jul/20 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Fausto Leyva (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Sprint: | Execution Team 2020-08-10 | ||||||||
| Participants: | |||||||||
| Description |
|
Take corrective action when there are incorrect multikey metadata keys here. |
| Comments |
| Comment by Louis Williams [ 24/Aug/20 ] |
|
Taking this out of the project because we have never observed customer issues with this, it is not explicitly required by the scope, and startup repair will still rebuild indexes if it detects this corruption scenario. |