HIVE-29654: Provide an easy way to execute a query and get the CBO plan at the same time#6556
Open
thomasrebele wants to merge 1 commit into
Open
HIVE-29654: Provide an easy way to execute a query and get the CBO plan at the same time#6556thomasrebele wants to merge 1 commit into
thomasrebele wants to merge 1 commit into
Conversation
…an at the same time
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What changes were proposed in this pull request?
Include the Calcite plan when enabling
hive.log.explain.output, as discussed in HIVE-29654.Why are the changes needed?
Make it easier to get the exact Calcite plan that has been used for an executed query.
Does this PR introduce any user-facing change?
Just adding the Calcite plan to the logging of
hive.log.explain.output.How was this patch tested?
Unit test and manual execution of a query in beeline.