Drop legacy shard catalog collections when upgrading

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • CAR Team 2026-06-22
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We drop the legacy collections (config.cache.catalog.*) when upgrading.

      We may also need to do so on downgrade, in case an unclean upgrade left some metadata in those collections, to ensure that the downgrade does not crash or operate on corrupted data. This is a best-effort measure for cases where the customer did not follow the proper upgrade procedure.

            Assignee:
            Joan Bruguera Micó
            Reporter:
            Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: