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

Update metadata manager tests that expect a collection description to hold a range preserver

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.0.5
    • Affects Version/s: 7.0.2
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • ALL
    • CAR Team 2023-11-27
    • 5

      7.0 only.

      In SERVER-79780, the getActiveMetadata function in the metadata manager was changed to add a boolean representing whether the range should be preserved. However, when backporting this to 7.0, some of the tests were not updated and so are using getActiveMetadata without getting a rangePreserver but expecting the range to be preserved.

      This ticket is to look through the metadata manager unit tests and see if any of them require preserveRange to be true (CleanupNotificationsAreSignaledWhenMetadataManagerIsDestroyed definitely does).

            Assignee:
            allison.easton@mongodb.com Allison Easton
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: