restarting the catalog should leave drop-pending idents intact

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.7
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Storage NYC 2018-12-31
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The existing behavior in restartCatalog removes any idents it does not recognize in the KV catalog. The KV storage engine will make a list of drop-pending idents available to restartCatalog so that drop-pending idents are not dropped during a restartCatalog operation.

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

              Created:
              Updated:
              Resolved: