[SERVER-81779] Investigate whether to sanitize collection options upon creation during moveChunk/movePrimary/resharding Created: 03/Oct/23  Updated: 02/Nov/23  Resolved: 02/Nov/23

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

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Jordi Olivares Provencio
Resolution: Won't Do Votes: 0
Labels: oldshardingemea, shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-72229 Implement FCV upgrade step to remove ... Closed
related to SERVER-79496 Ban encryption options being provided... Closed
Assigned Teams:
Catalog and Routing
Sprint: CAR Team 2023-11-13
Participants:
Story Points: 2

 Description   

SERVER-79496 banned some collection options related with encryption starting from v7.2 while SERVER-72229 added an FCV upgrade step in order to sanitize the catalog on all shards and get rid of such options.

As a result, it will not be possible to clone collections with such options while running under feature compatibility version v7.0 when using v7.2 binaries (and v8.0 binaries in the near future).

Purpose of this ticket is to audit all collection cloning procedures in the sharding codebase in order to make sure not to clone the banned collection options by sanitizing them using getSanitizedStorageOptionsForSecondaryReplication.



 Comments   
Comment by Jordi Olivares Provencio [ 02/Nov/23 ]

SERVER-82203 fixed the issue by adding a feature flag for the new behaviour. This flag is only enabled starting on 7.2 and is FCV gated. This is now a non-issue since the new options are scrubbed from all replicated collections after performing the FCV upgrade

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