[SERVER-27575] Segmentation fault when trying to use $bucketAuto with $max or $min operator in the output field Created: 04/Jan/17 Updated: 04/Jan/17 Resolved: 04/Jan/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | 3.4.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Charles Sarrazin (Inactive) | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||
| Steps To Reproduce: |
|
||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||
| Description |
|
It seems that using $max or $min in the output option of a $bucketAuto aggregation step triggers a segmentation fault. I managed to reproduce this issue with version 3.4.1-ent, and this script (replace $max by $min, to have the same behaviour):
Output:
The logs are attached to this ticket. |
| Comments |
| Comment by Charles Sarrazin (Inactive) [ 04/Jan/17 ] |
|
Thanks anonymous.user! |
| Comment by Kelsey Schubert [ 04/Jan/17 ] |
|
Hi charles.sarrazin, This issue will be corrected with the release of MongoDB 3.4.2. Please see Thank you, |