[SERVER-36804] No "executionStats" with explain mode for aggregate Created: 22/Aug/18 Updated: 23/Sep/18 Resolved: 26/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | 4.0.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | dorothee | Assignee: | Nick Brewer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
As describe here https://jira.mongodb.org/browse/SERVER-19758, the functionnality "executionStats" with explain has been added since Mongo version 3.5.5. With Mongo version 4.0.1, "executionStats" is not returned with explain mode.
Result method 1 :
|
| Comments |
| Comment by dorothee [ 27/Aug/18 ] | |
|
Thanks. Unfortunately, I use the latest version of Robo3T 1.2 for windows. As you suggest, my last chance is to ask them. | |
| Comment by Nick Brewer [ 26/Aug/18 ] | |
|
dorothee According to the Robo3T Github it embeds mongo shell version 3.4. However, you may have better luck asking this question within the Robo3T community. Since this doesn't demonstrate in MongoDB, I'll close this ticket. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. -Nick | |
| Comment by dorothee [ 24/Aug/18 ] | |
|
Thanks for your answer. You're right. It's probably due to the shell version, used by my client tool Robo3T. I did a test directly in command line on Mongo Server (MongoDB server version: 4.0.1,MongoDB shell version v4.0.1) where engine version and shell version are aligned The output of the command :
returns "executionStats" attibute as expected. A question in pending for me : how to know and change the mongo shell version used by Robo3T if it's possible. Dorothée
| |
| Comment by Nick Brewer [ 22/Aug/18 ] | |
|
dorothee I believe the issue here is that you're likely using an older driver, or an older version of the mongo shell. Could you try upgrading to the latest stable version of your driver / shell, and let us know if this resolves the issue? -Nick |