[SERVER-54010] Clustered indexes 'expireAfterSeconds' option can be modified by collMod Created: 25/Jan/21  Updated: 29/Oct/23  Resolved: 10/Feb/21

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

Type: New Feature Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-53984 Add metadata for clustered indexes in... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-02-22
Participants:

 Description   

The collMod command will need to allow the expireAfterSeconds option to be added, removed and modified on collections with clustered indexes. collMod will continue to take an exclusive lock on the collection during the procedure.

{
    collMod: <collection>,
    clusteredIndex: {
        expireAfterSeconds: <int>,
    },
}

collMod will return InvalidOptions when run against regular or non-existent collections. An expireAfterSeconds value of 0 will remove the expireAfterSeconds field from the durable catalog metadata.



 Comments   
Comment by Githook User [ 10/Feb/21 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-54010 Clustered indexes 'expireAfterSeconds' option can be modified by collMod
Branch: master
https://github.com/mongodb/mongo/commit/861023b28a5dc270d2c459194dab8ea72b3bb817

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