[SERVER-20267] Upconvert $explain option for OP_QUERY find to an explain command on mongos Created: 02/Sep/15 Updated: 19/Sep/15 Resolved: 03/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.8 |
| 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 |
|
Currently, if an OP_QUERY find is redirected to the new mongos read path, the $explain option will be ignored. We need to either explicitly error and require clients to use the explain command, or support $explain in the new path. |
| Comments |
| Comment by Githook User [ 12/Sep/15 ] |
|
Author: {u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}Message: libmongoscore intentionally depends on libcluster_query, but prior This issue is addressed by moving ClusterFind::runExplain() to |
| Comment by Githook User [ 03/Sep/15 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: |