[SERVER-14320] CollectionMetadata::keyBelongsToMe() should assert that given key is non-empty in debug builds Created: 19/Jun/14 Updated: 19/Oct/15 Resolved: 19/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
mongos enforces that documents modified in or inserted into sharded collections must have non-empty values for the shard key (though this is not enforced if mongos is bypassed). CollectionMetadata::keyBelongsToMe() could have a debug-only assert that fails the operation or terminates the process if a document is encountered that is missing the shard key. |