[SERVER-25430] Create a sharded collections passthrough of aggregation suite Created: 03/Aug/16 Updated: 19/Nov/16 Resolved: 30/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Tess Avitabile (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2016-10-10 |
| Participants: |
| Description |
|
Most of the integration testing of aggregation in a sharded cluster happens in jstests/aggregation/testshard1.js, but there are many other tests that are not stressing any logic in a sharded cluster, leading to bugs like We should create a passthrough suite that runs the aggregation tests against a sharded cluster, or move the agg tests to be part of the 'core' suite and leverage those existing passthroughs. The mongos does very little logic if the collection isn't sharded, so if we add a new passthrough, it should implicitly shard every collection to increase coverage. |
| Comments |
| Comment by Githook User [ 30/Sep/16 ] |
|
Author: {u'username': u'tessavitabile', u'name': u'Tess Avitabile', u'email': u'tess.avitabile@mongodb.com'}Message: |
| Comment by Charlie Swanson [ 11/Aug/16 ] |
|
As part of this ticket, we should remove this test |