[SERVER-2060] When enabling sharding in an existing collection, make sure all docs have values on the sharding keys Created: 03/Nov/10  Updated: 12/Jul/16  Resolved: 10/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: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

1) create collection x
2) add document

{ b: 1 }

3) create index

{ a : 1 }


4) shardcollection x



 Comments   
Comment by auto [ 10/Jan/11 ]

Author:

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

Message: SERVER-2060 test for null values at shardcollection time
https://github.com/mongodb/mongo/commit/6a6ad16702e90f0020e2a2a3e847830d2e05e108

Comment by auto [ 10/Jan/11 ]

Author:

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

Message: SERVER-2060 allow an index to be validated for sharding
https://github.com/mongodb/mongo/commit/95883498e57326ad0fedf111f65922c03ca0f356

Comment by Alberto Lerner [ 03/Nov/10 ]

Can scan the null entries and make sure they're empty.

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