Show join predicates in vt keys
and vt benchstat
#43
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Descrition
This PR is based on #42. And the vitess version used in the PR is based on vitessio/vitess#17130.
With this PR we can now list and summarize the usage of Join Predicate per table and per query. This will allow us to know exactly what join predicates we use per table/query and understand the relationship between the different tables present in the query log.
Results
For the following query:
We get the following output with
vt keys
:Which can then be fed to
vt benchstat
, and we get: