Remove the logic that explicitly drains back/forwards incompatible DDL requests during FCV transitions

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2025-06-09, CAR Team 2025-06-23
    • None
    • 3
    • TBD
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None
    • 0

      With the recent introduction of built-in FCV snapshots  in Sharding DDL coordinators, it is no longer needed to explicitly deal with the activation state of feature flags at DDL  request dispatching time (example) and the draining of back/forwards incompatible  requests upon a setFCV transition (example). 

      The objective of this ticket is to clean-up  related obsolete logic.

            Assignee:
            Paolo Polato
            Reporter:
            Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: