Optimise filtering metadata recovery after rename

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      With the implementation of authoritative rename we chose to not install the latest filtering metadata on the primary because it was easier to implement.

      This ticket is about deciding whether it makes sense to recover the filtering metadata once the metadata changes have been committed to disk.

            Assignee:
            Unassigned
            Reporter:
            Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: