insert operations may fail to set index to multikey after aborted multikey catalog update

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.0.2, 4.4.9, 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • v5.0, v4.4, v4.2, v4.0
    • Execution Team 2021-05-31, Execution Team 2021-06-14
    • 127
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When a storage transaction to update an index to multikey is aborted, it is possible for the in-memory state of an index to appear as multikey but the durable state to remain as non-multikey.

      In this scenario, the IndexCatalogEntryImpl (erroneous in-memory state) may contain path-level information which lead to this optimization being erroneously applied to subsequent multikey writes and leaving the index as non-multikey in the catalog.

              Assignee:
              Benety Goh
              Reporter:
              Benety Goh
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: