Keep track of multikey in resumable index build state

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.8.0
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2020-09-21
    • 31
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Gregory Noma
            Reporter:
            Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: