[DOCS-11949] Docs for SERVER-34489: Enable new format Unique Index via FCV Created: 07/Aug/18  Updated: 13/Nov/23  Resolved: 25/Oct/18

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.1.2, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: nonnyc, storage-engines
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-34489 Enable new format Unique Index via FCV Closed
Participants:
Days since reply: 5 years, 15 weeks, 6 days ago
Epic Link: DOCS: 4.2 Server/Tools

 Description   

----------------------------

Original Description

Description:

DOCS-11933 deals with the documentation changes required by this work.

Engineering Ticket Description:

New format unique indexes would be initially gated by a variable. Start using FCV to enable or disable new format unique indexes:

  • Plug-in new format indexes into upgrade/downgrade infratructure.
  • Setting FCV=4.2 will cause all exisinting unique indexes to be updated to new format. The content of indexes will not change. New entries will be in new format.
  • With FCV=4.0, existing new format index will remain in this format. Any new unique indexes will be created in old V2 format.
  • Enhance multiVersion test for collectionsPendingDrop.

----------------------------

Description

Scope of changes (files that need work and how much)

4.2-compat
4.2-downgrade
unique-index

Impact to other docs outside of this product

MVP (work and date?)

Resources (e.g. Scope Docs, Invision)



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

Author:

{'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-11949: 4.2 unique index internal format
Branch: master
https://github.com/mongodb/docs/commit/607d4e6435b6eeec06e34c37d636922a4cb03336

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