[SERVER-37905] dropCollection command clears metadata for unsharded collections Created: 02/Nov/18  Updated: 06/Dec/22  Resolved: 02/Nov/22

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

Type: Task Priority: Major - P3
Reporter: Misha Tyulenev Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Do Votes: 0
Labels: MaxH, pm-1051-legacy-tickets
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-37535 createCollection command needs to add... Closed
Assigned Teams:
Sharding
Sprint: Sharding 2018-11-19
Participants:

 Description   

Similar to the createCollection command SERVER-37535 dropCollection needs to support both sharded and unsharded collections.

Test

  1. Test that drop collection removes the entry from the config.collections


 Comments   
Comment by Max Hirschhorn [ 02/Nov/22 ]

Similar to SERVER-37535 a separate project will capture whatever work is eventually needed for all collections to be sharded upon creation.

Comment by Githook User [ 14/Jun/19 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: Revert "SERVER-37905 add regression tests for hyrid index builds."

This reverts commit 86ccf51acba7bbefca2b70333995de80c16e68be.
Branch: master
https://github.com/mongodb/mongo/commit/95095634ca2d1508058fd54d5389be371aab1e19

Comment by Githook User [ 14/Jun/19 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-37905 add regression tests for hyrid index builds.
Branch: master
https://github.com/mongodb/mongo/commit/86ccf51acba7bbefca2b70333995de80c16e68be

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