[SERVER-69072] Prohibit setting the 'expireAfterSecond' field if the change collection mode is not active Created: 23/Aug/22  Updated: 29/Oct/23  Resolved: 22/Sep/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Rishab Joshi (Inactive) Assignee: Romans Kasperovics
Resolution: Fixed Votes: 0
Labels: pm-2334-m2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: QE 2022-09-19, QE 2022-10-03
Participants:

 Description   

The expireAfterSeconds change streams parameter will be available to the setClusterParameter command in version 6.1. The CWC currently does not support gating configuration via FCVs as such the user can set this configuration in version 6.1. While rolling the expireAfterSeconds configuration in v6.1 should not be an issue in the field, we should still ensure that this parameter can only be used after the PM-2334 is enabled. This is in accordance with the CWC recommendation.

PM-2334 project will potentially be released at/after v6.2. We should continue to block setting this parameter until the feature flag/fcv_6.2 is enabled.

 

As part of this ticket, we should also ensure that pre-images.expireAfterSeconds CWC parameter cannot be set in the serverless, this is because in the serverless we will use changeStreams.expireAfterSeconds to set retention time for the change collection and the pre-images collection.



 Comments   
Comment by Githook User [ 22/Sep/22 ]

Author:

{'name': 'Romans Kasperovics', 'email': 'romans.kasperovics@mongodb.com', 'username': 'romanskas'}

Message: SERVER-69072 Add version restrictions to change stream expireAfterSeconds parameters
Branch: master
https://github.com/mongodb/mongo/commit/b99c0f1cbf37d0e1c14cf19407eea1ce4ccabc5e

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