[SERVER-64617] [5.3] Allow new unique index data formats to exist Created: 17/Mar/22  Updated: 29/Oct/23  Resolved: 05/Apr/22

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

Type: Task Priority: Major - P3
Reporter: Yuhong Zhang Assignee: Yuhong Zhang
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-63577 Ensure that new unique indexes don't ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-03-21, Execution Team 2022-04-04, Execution Team 2022-04-18
Participants:

 Description   

We are introducing unique index data format 13 and 14 on 6.0. As a result, we would also allow the new data formats to exist on 5.3 for downgrade compatibility. However, we will still use only data format 11 and 12 when creating and modifying indexes on 5.3.

Also, the master branch code will need the support on 5.3 to pass the multiversion tests.



 Comments   
Comment by Githook User [ 05/Apr/22 ]

Author:

{'name': 'Yuhong Zhang', 'email': 'yuhong.zhang@mongodb.com', 'username': 'YuhongZhang98'}

Message: SERVER-64617 Allow new unique index data formats to exist
Branch: v5.3
https://github.com/mongodb/mongo/commit/a9687768331c2884fb127721fae2e4b212b6f17f

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