Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-88030

dump_coll_metadata.js should expect collection metadata to became unknown after shardCollection

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2024-03-18, CAR Team 2024-04-01
    • 43

      In SERVER-80135 we made so that shardCollection operation will clear the filtering metadata (setting the metadata on the CSR to UNKNOWN) and then trigger a best effort refresh.

      dump_coll_metadata.js test is wrongly assuming that after a shardCollection the collection metadata on the shard will always be present.

            Assignee:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Reporter:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: