[SERVER-81281] Add query shape hash to output of $queryStats Created: 20/Sep/23 Updated: 13/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
We discussed with members of the query team working on related projects (persistent query settings and the plan cache), and this seems like a valuable place to put this information. It should be fairly cheap to compute, and doing so at read time (when invoking $queryStats) is not a performance concern (compared to doing so during the processing of each query, which we were doing for a little while). |
| Comments |
| Comment by Charlie Swanson [ 04/Oct/23 ] |
|
update: denis.grebennicov@mongodb.com says there are ongoing discussions about exactly which hash to use and whether we want this particular thing. I think it is relatively easy to do now or later, so we'll wait for the clear picture. I think this means we should kick it out of our project and into PM-412, so I will do so now. Let me know if we have a clearer answer soon and we should do it as part of our project though. |