[SERVER-54132] Review usages of config.collections 'dropped' field Created: 29/Jan/21  Updated: 29/Oct/23  Resolved: 19/Feb/21

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

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Jordi Serra Torrens
Resolution: Fixed Votes: 0
Labels: Sharding-EMEA, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-51900 Get rid of the "distributionMode" fie... Closed
Related
is related to SERVER-54629 Remove skip indexConsistencyCheck in ... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

As part of SERVER-51900, the dropped field has been removed from config.collections. There are some remaining usages that should be removed, for example in the method to check if a collection is sharded in the shell (currently making getShardDistribution silently fail).

To find all usages, the following grep should be enough:

git grep '\.dropped\|dropped:'



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

Author:

{'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}

Message: SERVER-54132: Review usages of config.collections 'dropped' field
Branch: master
https://github.com/mongodb/mongo/commit/822232665be8d186ae5801659221197a19180aef

Comment by Max Hirschhorn [ 29/Jan/21 ]

Later versions of the mongo shell tend to be compatible with earlier versions of the server. I think we may want to keep some of the checking for {dropped: false} and also allow for {dropped: {$exists: false}}.

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