[SERVER-20537] Re-enable tests disabled when OP_QUERY legacy ops in mongos are made to use new find command path Created: 21/Sep/15 Updated: 07/Oct/15 Resolved: 30/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | J Rassi |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | QuInt A (10/12/15) |
| Participants: |
| Description |
|
This is a placeholder ticket to re-enable any tests disabled (and fix any bugs discovered) as part of enabling the new find command path in mongos for OP_QUERY legacy user queries. |
| Comments |
| Comment by Githook User [ 24/Sep/15 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: If ARM::kill() was called before the find command response was received, the callback for the |