Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.0.9, 3.1.4
Affects Version/s: None
Component/s: Aggregation Framework
Labels:
None

Backwards Compatibility:
Fully Compatible
Backport Completed:

3.0.9
Sprint:
Quint Iteration 3, Quint Iteration 4
Confidence Status:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

If only one shard is involved in an aggregate operation, handle this like an aggregation on non-sharded setups.

This will improve performance and reduce memory and network activity for many sharded setups, where the shardkey is for example the userId.

is related to

SERVER-18940 Optimise sharded aggregations that are targeted to a single shard

Closed

related to

SERVER-18444 Improve explain output of aggregation command in sharded cluster

Closed

SERVER-23330 Optimize aggregation on sharded setup if first stage is exact match on shard key with $in

Closed

Assignee:: Charlie Swanson

Reporter:: Gernot Pansy

Participants:: Charlie Swanson, Gernot Pansy, Githook User

Votes:: 0 Vote for this issue

Watchers:: 9 Start watching this issue

Created:: Nov 13 2012 11:07:27 PM UTC

Updated:: Mar 24 2016 01:14:31 PM UTC

Resolved:: May 28 2015 04:47:20 PM UTC

Confidence Status Last Update:: 12/May/15 8:02 PM