-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
ALL
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.
- is depended on by
-
SERVER-1817 A collection exists but the field "dropped" in "config.collections" is true
- Closed