[SERVER-3743] hasShardKey should return false for non-exact queries on shardkey Created: 01/Sep/11 Updated: 11/Jul/16 Resolved: 06/Feb/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
currently returns true for things like {key:{$exists:true}}. If the value is an object need to make sure key name doesn't start with $. |
| Comments |
| Comment by auto [ 06/Feb/12 ] |
|
Author: {u'login': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: hasShardKey should return false if using $ops |
| Comment by Mathias Stearn [ 02/Feb/12 ] |
|
Taking this back and bumping to 2.1.1 since it is trivial and makes one of my other cases simpler |
| Comment by Eliot Horowitz (Inactive) [ 01/Sep/11 ] |
|
When we do this, we need to make sure all callers of this method are ok with that, since that is not exactly what the docs say it does now. |