[SERVER-55585] Improve readability of index KeyString values in SBE explain output Created: 29/Mar/21 Updated: 20/May/21 Resolved: 17/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Query Execution |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Anton Korshunov | Assignee: | Jennifer Peshansky (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | post-rc0, sbe-post-rc0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Query Execution 2021-05-03, Query Execution 2021-05-17, Query Execution 2021-05-31 |
| Participants: |
| Description |
|
Currently when we include an index key value in SBE explain output, we dump it as an encode KeyString value, which is not very useful for debugging, as you always need to decipher it to figure out what the bounds were. It would be useful to include a rehydrated index key along with a KeyString. For example: KS(2B022B020104) [1,1].
|
| Comments |
| Comment by Jennifer Peshansky (Inactive) [ 17/May/21 ] |
|
In order to retrieve the index from the KeyString, we would need to pass the ordering/key pattern as a parameter to 'writeValueToStream', and this new parameter would only be applicable to KeyStrings in a method that is used for many different data types. This is undesirable, and therefore it is not feasible to retrieve the rehydrated index keys. |