[SERVER-24097] Add special handling for --repair and "repairable" feature bits set in the KVCatalog Created: 08/May/16  Updated: 06/Dec/22  Resolved: 10/Jun/19

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

Type: New Feature Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Backlog - Storage Execution Team
Resolution: Won't Do Votes: 0
Labels: todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-23116 Add versioning scheme to the KVCatalo... Closed
Related
related to SERVER-43433 Remove TODO referencing SERVER-24097 Backlog
Assigned Teams:
Storage Execution
Participants:

 Description   

Based on the design discussion for the KVCatalog versioning scheme, the feature document in SERVER-23116 has separate fields for "repairable" and "non-repairable" feature bits. The distinction between the "repairable" and "non-repairable" feature bits is that the "repairable" features are no longer in use after dropping and re-creating the indexes on the collection with an older version of MongoDB. A user would then be able to downgrade to an older version of MongoDB that didn't recognize the new feature by first running --repair.



 Comments   
Comment by Eric Milkie [ 10/Jun/19 ]

We don't believe we'll need this behavior in the future.

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