[SERVER-54354] New create collection path does not check for disable feature flag Created: 05/Feb/21  Updated: 06/Dec/22  Resolved: 11/Feb/21

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

Type: Bug Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-54283 Move the legacy dropDatabase/Collecti... Closed
Problem/Incident
is caused by SERVER-52616 Create the _shardsvrCreateCollection ... Closed
Assigned Teams:
Sharding
Operating System: ALL
Participants:
Linked BF Score: 27

 Description   

The new create collection path currently is only checking for the shardingFullDDLsupport feature flag, however, some suites with stepDowns or kill primaries might fail because the POS is not implemented yet. The disableIncompleteShardingDDLSupport currently used only on the new drop collection path can be added to address this tests.



 Comments   
Comment by Marcos José Grillo Ramirez [ 11/Feb/21 ]

This ticket was solved as part of the ticket SERVER-54283

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