[SERVER-51891] Make ShardCollectionType not use strict parsing Created: 30/Oct/20  Updated: 29/Oct/23  Resolved: 18/Nov/20

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

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Sergi Mateo Bellido
Resolution: Fixed Votes: 0
Labels: PM-1965-Cleanup
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-50027 Freeze migrations on original sharded... Closed
Related
related to SERVER-53052 Review some recent changes introduced... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-11-02, Sharding 2020-11-16, Sharding 2020-11-30
Participants:

 Description   

Currently, the IDL parser for ShardCollectionType doesn't specify {strict:false}, which means it explicitly performs strict parsing. This makes it impossible to add new fields to that structure.

As part of this ticket we should do the following:

  • Add {strict:false}
  • Add an FCV 5.0 -> 4.4 downgrade step on the shards, which clears any newly added fields (e.g., SERVER-50027) from config.cache.collections so that 4.4 binaries can parse them.


 Comments   
Comment by Max Hirschhorn [ 18/Nov/20 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-51891 Make ShardCollectionType not use strict parsing

Comment by Githook User [ 02/Nov/20 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-51891 Make ShardCollectionType not use strict parsing (PART 1)

This commit only takes care of removing the strict parsing of
ShardCollectionTypeBase. We still need to take care of the downgrading
process: we will have to remove the new fields so old binaries can
properly parse them
Branch: master
https://github.com/mongodb/mongo/commit/4d2dea00415bf02d2b32d0474c93d251ce6568cc

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