[SERVER-32690] Aggregation can trip invariant related to renamed fields optimization Created: 12/Jan/18 Updated: 30/Oct/23 Resolved: 19/Jan/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework, Stability |
| Affects Version/s: | 3.6.2 |
| Fix Version/s: | 3.6.3, 3.7.2 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Aidan SE Mahler [X] | Assignee: | David Storch |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 16.04.3 LTS |
||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v3.6
|
||||||||||||||||
| Steps To Reproduce: | Include these stages in the db.collection.aggregate method:
Example:
|
||||||||||||||||
| Sprint: | Query 2018-01-29 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Running certain db.collection.aggregate commands causes the mongod process to crash. Specifically, the crash seems to occur when field names contain a colon (:). Error output:
|
| Comments |
| Comment by Githook User [ 22/Jan/18 ] | ||||||||||||||
|
Author: {'name': 'David Storch', 'email': 'david.storch@10gen.com', 'username': 'dstorch'}Message: (cherry picked from commit 92d58a1815b917d165c39235f9fe5b8a319072c3) Conflicts: | ||||||||||||||
| Comment by Githook User [ 19/Jan/18 ] | ||||||||||||||
|
Author: {'name': 'David Storch', 'email': 'david.storch@10gen.com', 'username': 'dstorch'}Message: | ||||||||||||||
| Comment by Aidan SE Mahler [X] [ 13/Jan/18 ] | ||||||||||||||
|
Interesting. I thought that it was specific to field name with colons, but you are right that others cause the failure as well (foobar, bar, and ar cause failure, while foo, fooba, and var do not). Glad that the root cause has been identified. | ||||||||||||||
| Comment by David Storch [ 12/Jan/18 ] | ||||||||||||||
|
Thanks for the report. We have identified a fix and will be working to get it merged and backported. It looks like this was introduced by I can reproduce with this minimal repro:
|