## Querying 

• SERVER-15287 416 Query planner sort analysis incorrectly allows index key pattern plugin fields to provide sort 

• SERVER-15286 417 Assertion in date indexes when opposite-direction-sorted and double “or” filtered 

• SERVER-15279 418 Disable hash-based index intersection (AND_HASH) by default 

• SERVER-15152 419 When evaluating plans, some index candidates cause complete index scan 

• SERVER-15015 420 Assertion failure when combining $max and $min and reverse index scan 

• SERVER-15012 421 Server crashes on indexed rooted $or queries using a 2d index 

• SERVER-14969 422 Dropping index during active aggregation operation can crash server 

• SERVER-14961 423 Plan ranker favors intersection plans if predicate generates empty range index scan 

• SERVER-14892 424 Invalid {$elemMatch: {$where}} query causes memory leak 

• SERVER-14706 425 Queries that use negated $type predicate over a field may return incomplete results when an index is present on that field 

• SERVER-13104 426 Plan enumerator doesn’t enumerate all possibilities for a nested $or 

• SERVER-14984 427 Server aborts when running $centerSphere query with NaN radius 

• SERVER-14981 428 Server aborts when querying against 2dsphere index with coarsestIndexedLevel:0 

• SERVER-14831 429 Text search trips assertion when default language only supported in textIndexVersion=1 used 

## Replication 

• SERVER-15038 430 Multiple background index builds may not interrupt cleanly for commands, on secondaries 

• SERVER-14887 431 Allow user document changes made on a 2.4 primary to replicate to a 2.6 secondary 

• SERVER-14805 432 Use multithreaded oplog replay during initial sync 

## Sharding 

• SERVER-15056 433 Sharded connection cleanup on setup error can crash mongos 

• SERVER-13702 434 Commands without optional query may target to wrong shards on mongos 

