[SERVER-70195] Two no-indexes ComparableIndexVersions should compare as the same Created: 04/Oct/22  Updated: 29/Oct/23  Resolved: 25/Oct/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Allison Easton Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: PM-2583-Milestone-2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31
Participants:

 Description   

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


 Comments   
Comment by Githook User [ 25/Oct/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-70195 Two no-indexes ComparableIndexVersions should compare as the same
Branch: master
https://github.com/mongodb/mongo/commit/25ca5c94af54c6d23554767b14d6229d2e900159

Generated at Thu Feb 08 06:15:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.