[SERVER-32821] Support rolling upgrade to new unique index format Created: 22/Jan/18  Updated: 30/Oct/23  Resolved: 02/Mar/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 3.7.3

Type: Improvement Priority: Major - P3
Reporter: Alexander Gorrod Assignee: Neha Khatri
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-32822 Support reading from unique indexes w... Closed
Related
related to SERVER-75922 Partial unique indexes created on Mon... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage 2018-02-26, Storage Non-NYC 2018-03-12
Participants:

 Description   

We are adding a new unique index format to support secondary apply with timestamps. The new format will remain compatible with the old format. This ticket encapsulates adding support for inserting into indexes created in the old format:

  • Create a test that populates a unique index in the old format, then switches to the new format and starts inserting data. (Don’t try to hook up FCV yet - that comes later, so another mechanism will be required in local testing).
  • Have the insert/update path identify when an old-version entry exists and remove it, prior to doing an insert.
  • There should be no additional work to support secondaries, but they should be tested at this stage.


 Comments   
Comment by Githook User [ 02/Mar/18 ]

Author:

{'email': 'neha.khatr@mongodb.com', 'name': 'nehakhatri5'}

Message: SERVER-32821 Insert and remove support for multiversion unique index.

During rolling upgrade unique index can have entries with both old and
new format index key. Support insert and remove for multiversion index.
Branch: master
https://github.com/mongodb/mongo/commit/80bf700fbb9f8fb3e71fe88888f3a7fb69450ef7

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