[SERVER-1849] Recreating recently dropped collection with different sharding parameters is not working Created: 24/Sep/10  Updated: 12/Jul/16  Resolved: 13/Jan/11

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

Type: Bug Priority: Major - P3
Reporter: Alberto Lerner Assignee: Alberto Lerner
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-1817 A collection exists but the field "dr... Closed
Operating System: ALL
Participants:

 Description   

Let's say I have sharded the collection "mydb.foo" before, loaded data
into it, and found out that I made a mistake in the sharding key I
used. I can drop "mydb.foo", but then I cannot remove the sharding
configuration on that collection. This means even if I create a new
collection named "mydb.foo" I still get the same old wrong sharding
configuration.



 Comments   
Comment by auto [ 13/Jan/11 ]

Author:

{u'login': u'alerner', u'name': u'Alberto Lerner', u'email': u'alerner@10gen.com'}

Message: SERVER-1849 tighten non-sharded access to a sharded server and make test clearer
https://github.com/mongodb/mongo/commit/a4c04f51cbe90dbb26efeb7abf02098f7faf1740

Comment by auto [ 03/Dec/10 ]

Author:

{'login': 'alerner', 'name': 'Alberto Lerner', 'email': 'alerner@10gen.com'}

Message: SERVER-1849 test case is exposing access to dropped collection (not yet fixed)
/mongodb/mongo/commit/4a9a5f19759e58b60c47d870d07d62db9fe767ec

Comment by auto [ 26/Nov/10 ]

Author:

{'login': 'alerner', 'name': 'Alberto Lerner', 'email': 'alerner@10gen.com'}

Message: SERVER-1849 comment
/mongodb/mongo/commit/b4be994a8e71777e3618cde219ec6c8220d40239

Comment by auto [ 26/Nov/10 ]

Author:

{'login': 'alerner', 'name': 'Alberto Lerner', 'email': 'alerner@10gen.com'}

Message: SERVER-1849 check for dropped collections
/mongodb/mongo/commit/78e92c49fed71f98bce8f67aedaa038b9a7569fe

Comment by auto [ 20/Nov/10 ]

Author:

{'login': 'alerner', 'name': 'Alberto Lerner', 'email': 'alerner@10gen.com'}

Message: SERVER-1849 Just to tie code site to the JIRA item
/mongodb/mongo/commit/43003e02356aa4b3f0c20e2f8a93d9cfc63a0160

Comment by auto [ 19/Nov/10 ]

Author:

{'login': 'alerner', 'name': 'Alberto Lerner', 'email': 'alerner@10gen.com'}

Message: SERVER-1849 Just to tie code site to the JIRA item
/mongodb/mongo/commit/43003e02356aa4b3f0c20e2f8a93d9cfc63a0160

Comment by Alberto Lerner [ 19/Nov/10 ]

reopening to investigate shard3.js failure.

Comment by auto [ 27/Sep/10 ]

Author:

{'login': 'alerner', 'name': 'Alberto Lerner', 'email': 'alerner@10gen.com'}

Message: SERVER-1849 allow recreating a recently dropped collection
http://github.com/mongodb/mongo/commit/d260bd608659d0a4610cdcec3ca9e355b18bf9b2

Comment by auto [ 25/Sep/10 ]

Author:

{'login': 'alerner', 'name': 'Alberto Lerner', 'email': 'alerner@10gen.com'}

Message: SERVER-1849 allow recreating a recently dropped collection
http://github.com/mongodb/mongo/commit/e8f0119c5546f9133709ef82b42a1947f66aa494

Generated at Thu Feb 08 02:58:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.