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

Two no-indexes ComparableIndexVersions should compare as the same

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31

      As part of changing the CollectionIndexes to use the UUID instead of the CollectionGeneration, we will need to update the ComparableIndexVersion.

      As part of this ticket we need to:

      • Make the comparableIndexVersion contain only the index timestamp and a forced refresh sequence number
      • Change the comparison of ComparableIndexVersions so that all boost::none index versions compare as the same
      • Ensure that any transition from boost::none -> valid timestamp or timestamp -> boost::none triggers a refresh
      • Modify the index cache to make the GlobalIndexesCache optional --> we should not get a GlobalIndexesCache object from the cache if the time in store is boost::none

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

              Created:
              Updated:
              Resolved: