[SERVER-6118] aggregation returns incorrect results for sharded sorts Created: 18/Jun/12 Updated: 11/Jul/16 Resolved: 16/Jul/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | 2.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
The aggregation framework appears to distribute sorts to each shard and return sorted results from each shard sequentially, without ensuring that the combined result set is sorted. Group, in contrast to sort, seems to be handled specifically within mongos. Test:
Observed behavior: The results of a sharded sort aggregation may not be properly sorted. |
| Comments |
| Comment by auto [ 16/Jul/12 ] |
|
Author: {u'date': u'2012-07-16T14:21:01-07:00', u'email': u'mathias@10gen.com', u'name': u'Mathias Stearn'}Message: Make test for |
| Comment by auto [ 10/Jul/12 ] |
|
Author: {u'date': u'2012-07-06T17:56:22-07:00', u'email': u'mathias@10gen.com', u'name': u'Mathias Stearn'}Message: |
| Comment by auto [ 10/Jul/12 ] |
|
Author: {u'date': u'2012-07-06T17:09:58-07:00', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Make Pipeline::splitForSharded not O(n^2). Prep for |