[SERVER-20719] Introduce variant of sharding_jscore_passthrough configured to use "legacy" (OP_QUERY) readMode Created: 01/Oct/15 Updated: 15/Oct/15 Resolved: 07/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Sharding, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | David Storch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QuInt A (10/12/15) |
| Participants: |
| Description |
|
This will ensure coverage of the scenario where a sharded cluster has been upgraded to 3.2 but the driver does not support the find/getMore commands. We should also change the "sharding_legacy" suite to use readMode "commands" rather than readMode "legacy", since we want test coverage of SCCC mode config servers combined with an upgraded driver that issues find/getMore commands. |
| Comments |
| Comment by Githook User [ 07/Oct/15 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: This is a variant of the sharding jsCore passthrough suite that is |