Consider removing clone_authoritative_db_metadata.js test

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2025-03-31
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Once the upgrade/downgrade process for authoritative database metadata shards is complete, we will have a comprehensive set of tests that trigger the full procedure, including cloning from the global catalog to the shard-local catalog.

      However, to work incrementally, we currently have the clone_authoritative_db_metadata.js test, which internally verifies how this DDL should behave. Since we will have broader test coverage for this functionality, we may want to remove this test.

            Assignee:
            Pol Pinol
            Reporter:
            Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: