[SERVER-20289] Create a sharding passthrough that implicitly shards collections Created: 03/Sep/15 Updated: 06/Feb/17 Resolved: 29/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Testing Infrastructure |
| Affects Version/s: | 3.1.7 |
| Fix Version/s: | 3.1.9 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kamran K. | Assignee: | Robert Guo (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | TIG 9 (09/18/15), TIG A (10/09/15) | ||||||||
| Participants: | |||||||||
| Description |
|
The sharding_jscore_passthrough suite enables sharding for the 'test' database and then runs a subset of the jsCore tests against the same sharded cluster. We can improve our test coverage of sharded commands by creating a new passthrough that overrides the DBCollection prototype to automatically shard any collection that's used by a jsCore test. We should test with a hashed shard key and an _id shard key. |
| Comments |
| Comment by Githook User [ 29/Sep/15 ] |
|
Author: {u'username': u'guoyr', u'name': u'Robert Guo', u'email': u'robert.guo@10gen.com'}Message: |