[SERVER-56483] SBE explain output for ixscan/ixseek stage should indicate which index is being read Created: 29/Apr/21 Updated: 29/Oct/23 Resolved: 07/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0, 5.1.0-rc3 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | Bobby Morck (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v5.1
|
||||||||||||
| Sprint: | QE 2021-10-04, QE 2021-10-18 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
When an SBE plan involves in ixscan or ixseek stage, the explain output associated with that stage looks something like this:
Notably absent from this output is any indication of what the index is. We should include the index name and/or key pattern. For comparison, here is what the output from the classic engine's IXSCAN stage looks like:
We should consider adding the following information to SBE explain output for ixscan/ixseek as part of this ticket:
|
| Comments |
| Comment by Githook User [ 01/Nov/21 ] |
|
Author: {'name': 'Bobby Morck', 'email': 'bobby.morck@mongodb.com', 'username': 'bmorck'}Message: |
| Comment by Githook User [ 07/Oct/21 ] |
|
Author: {'name': 'Bobby Morck', 'email': 'bobby.morck@mongodb.com', 'username': 'bmorck'}Message: |
| Comment by Anton Korshunov [ 04/May/21 ] |
|
This information is available in the explain output under the queryPlanner section, so I personally don't see a huge value duplicating this info in the executionStats section. An ixscan/ixseek can always be mapped to a corresponding IXSCAN QSN from where one can pull the index name. |
| Comment by Alex Bevilacqua [ 04/May/21 ] |
|
ana.meza including this information per ixscan/ixseek will facilitate visual and tool-based parsing of these plans so I would say yes, it's important |
| Comment by Ana Meza [ 04/May/21 ] |
|
Adding christopher.harris alex.bevilacqua, could you please advise if this is important? Thanks |