[SERVER-13890] Index bounds builder constructs invalid bounds for multiple negations joined by an $or Created: 09/May/14 Updated: 11/Jul/16 Resolved: 09/May/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Querying |
| Affects Version/s: | 2.6.0, 2.6.1 |
| Fix Version/s: | 2.6.2, 2.7.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ranjith Ramachandra | Assignee: | David Storch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Backport Completed: | |||||||||
| Steps To Reproduce: |
|
||||||||
| Participants: | |||||||||
| Description |
| Comments |
| Comment by Billy Tetrud [ 25/Jan/16 ] | ||||
|
I'm still using version 2.4.0, but I'm planning on updating in the next couple days because I'm running across this bug. I'm hopeful that because the issue in this ticket was fixed that my issue will be too. | ||||
| Comment by Ramon Fernandez Marina [ 25/Jan/16 ] | ||||
|
fresheneesz, I'm not able to trigger an assertion error using your example. What version of MongoDB are you using and what's the exact behavior you're seeing? If you could open a new SERVER ticket with this information it would make it easier to investigate further. Thanks, | ||||
| Comment by Billy Tetrud [ 23/Jan/16 ] | ||||
|
For anyone still on an old version, its not just multiple negations that triggered this problem. I also got it with something like this:
| ||||
| Comment by Atul Kachru [ 05/Aug/14 ] | ||||
|
CAP ticket added. | ||||
| Comment by Githook User [ 16/May/14 ] | ||||
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: | ||||
| Comment by Githook User [ 09/May/14 ] | ||||
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: | ||||
| Comment by David Storch [ 09/May/14 ] | ||||
|
Hi ranjith19, thanks for reporting this bug. I have confirmed that this issue still exists, and can reproduce it locally using these steps:
The problem is related to how we construct index bounds in the presence of multiple negations joined by an $or. | ||||
| Comment by Ranjith Ramachandra [ 09/May/14 ] | ||||
|
Sorry for not formatting the issue correctly. But I could not figure how to do it |