[SERVER-15020] Implement explain for the distinct command Created: 25/Aug/14  Updated: 22/Mar/17  Resolved: 11/Aug/15

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 3.1.7

Type: New Feature Priority: Major - P3
Reporter: J Rassi Assignee: Qingyang Chen
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-5960 Document explain for distinct command Closed
Duplicate
is duplicated by SERVER-9126 Cannot get query plan or status for d... Closed
Related
related to SERVER-19907 Distinct command should accept a BSON... Closed
related to SERVER-19983 Performance Regression in Mongo-perf ... Closed
is related to SERVER-10448 Revamp explain() formatting Closed
Backwards Compatibility: Fully Compatible
Sprint: QuInt 8 08/28/15
Participants:

 Comments   
Comment by Githook User [ 11/Aug/15 ]

Author:

{u'username': u'coollog', u'name': u'Qingyang Chen', u'email': u'qingyang.chen@10gen.com'}

Message: SERVER-15020 Added missing explain stats for distinct command
Branch: master
https://github.com/mongodb/mongo/commit/f9904bce323dc4c45e0669043fa0c94304d18c6d

Comment by David Storch [ 05/Aug/15 ]

qingyang.chen, re-opening for 3.1.8 as I think there is some additional work left to do. If you compare the stats reported in "executionStats" mode for IXSCAN and DISTINCT_SCAN, you'll see that there is much less information in the distinct case. We need to update Explain::statsToBSON() to add the missing information for DISTINCT_SCAN.

Comment by Githook User [ 31/Jul/15 ]

Author:

{u'username': u'coollog', u'name': u'Qingyang Chen', u'email': u'qingyang.chen@10gen.com'}

Message: SERVER-15020 Explain for distinct command
Branch: master
https://github.com/mongodb/mongo/commit/bc4572c985a6d9dca5721ec45e88a19061f3842e

Comment by David Storch [ 21/Jul/15 ]

qingyang.chen, let's talk to go over what's involved to complete this ticket.

Generated at Thu Feb 08 03:36:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.