[SERVER-27649] Don't error on serialization of $elemMatch with $regex Created: 12/Jan/17 Updated: 05/Jan/18 Resolved: 19/Jan/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 3.4.1 |
| Fix Version/s: | 3.4.2, 3.5.2 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Claudio Petrini | Assignee: | James Wahlin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||||||||||||||
| Steps To Reproduce: | On Mongo v3.4.1 execute the following query:
The collection queried has indexes as described in the description, the error happens only when sorting with this value {_id : 1} |
||||||||||||||||||||||||
| Sprint: | Query 2017-01-23 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||
| Description |
|
Hi, The collection on which the query is executed has the following indexes :
This error happens only when the sort query parameter is configured to {_id : 1}. |
| Comments |
| Comment by Githook User [ 19/Jan/17 ] | ||
|
Author: {u'username': u'jameswahlin', u'name': u'James Wahlin', u'email': u'james.wahlin@10gen.com'}Message: (cherry picked from commit 04b16905b7c3b6b3fce5fbc7f6ba17522311a7c4) | ||
| Comment by Githook User [ 19/Jan/17 ] | ||
|
Author: {u'username': u'jameswahlin', u'name': u'James Wahlin', u'email': u'james.wahlin@10gen.com'}Message: | ||
| Comment by James Wahlin [ 17/Jan/17 ] | ||
|
The currently planned fix for this issue may address | ||
| Comment by David Storch [ 12/Jan/17 ] | ||
|
Hi claudio.petrini@stamplay.com, Thanks for the detailed bug report. I can reproduce this assertion failure as follows:
This looks like an issue with the MatchExpression serialization improvements made for 3.4 under Best, |