[SERVER-2935] shallow woEqual check used for index dup checking Created: 12/Apr/11 Updated: 12/Jul/16 Resolved: 01/Jun/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.9.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Dwight Merriman |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Dwight noticed this yesterday. We probably want to do woCompare to handle cases like int/double comparison. bool BtreeBucket::exists(const IndexDetails& idx, const DiskLoc &thisLoc, const BSONObj& key, const Ordering& order) const { // skip unused keys return false; bool BtreeBucket::wouldCreateDup( while ( !b.isNull() ) { b = bucket->advance(b, pos, 1, "BtreeBucket::dupCheck"); return false; |
| Comments |
| Comment by auto [ 01/Jun/11 ] |
|
Author: {u'login': u'dwight', u'name': u'dwight', u'email': u'dwight@10gen.com'}Message: |
| Comment by Dwight Merriman [ 13/May/11 ] |
|
@mathias yes - want to make a jira for that or something? or just do it if you can in 5 minutes. |
| Comment by Mathias Stearn [ 12/May/11 ] |
|
We should probably also consider reversed indexes to be dups so people don't have both {a:1}and {a:-1} |