[SERVER-50899] Keep track of multikey in resumable index build state Created: 11/Sep/20 Updated: 29/Oct/23 Resolved: 15/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.8.0 |
| 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 | ||||
| Sprint: | Execution Team 2020-09-21 | ||||
| Participants: | |||||
| Linked BF Score: | 31 | ||||
| Description |
|
If a resumable index build was interrupted for shutdown after it was already determined to be multikey, that information may be lost when resuming the index build. We should store whether the index was already determined to be multikey along with the multikey paths in the state written to disk that is used to resume the index build. |
| Comments |
| Comment by Githook User [ 15/Sep/20 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |