Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.4.2, 3.5.2
Affects Version/s: None
Component/s: Aggregation Framework
Labels:
None

Backwards Compatibility:
Fully Compatible
Backport Completed:

3.4.2
Sprint:
Query 2016-11-21, Query 2016-12-12, Query 2017-01-23

Before ~~SERVER-25038~~ we were parsing the aggregation pipeline before we acquired the collection lock, and thus before we knew whether there was a default collation to use, so we added injectExpressionContext() as a callback to inform the pipeline of the new collation (if necessary). Once ~~SERVER-25038~~ is resolved, we can remove injectExpressionContext(), and make everything that might make string comparisons take an ExpressionContext as an argument to the constructor/parser, thus ensuring all comparisons can use the correct collation.

is duplicated by

SERVER-27395 $bucketAuto aggregation with $addToSet output accumulator crashes mongod

Closed

SERVER-27537 Seg fault with $max and $bucketAuto

Closed

SERVER-27575 Segmentation fault when trying to use $bucketAuto with $max or $min operator in the output field

Closed

SERVER-27579 $bucketAuto with ouput accumulator $max causes SIGSEV

Closed

SERVER-27626 Segfault when using $bucketAuto with $min in output

Closed

SERVER-27518 max accumulator with auto-buckets can cause mongod crash

Closed

related to

SERVER-27201 $graphLookup triggers null pointer dereference

Closed

(1 is duplicated by, 1 related to)

Assignee:: Charlie Swanson

Reporter:: Charlie Swanson

Participants:: Aaron Queen, Charlie Swanson, David Storch, Githook User

Votes:: 0 Vote for this issue

Watchers:: 9 Start watching this issue

Created:: Aug 10 2016 06:10:14 PM UTC

Updated:: Apr 05 2017 11:43:40 AM UTC

Resolved:: Dec 16 2016 09:25:11 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates