HIVE-29250: Display effects of PlanModifierForASTConv in EXPLAIN CBO output #6118
Conversation
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
|
kasakrisz
reviewed
Oct 13, 2025
| POSTHOOK: type: QUERY | ||
| POSTHOOK: Input: default@alter_coltype | ||
| #### A masked pattern was here #### | ||
| OPTIMIZED SQL: SELECT COUNT(*) AS `$f0` |
There was a problem hiding this comment.
Maybe we can wait for the conclusion of https://issues.apache.org/jira/browse/HIVE-29257 and these OPTIMIZED SQL: lines would go away.
kasakrisz
approved these changes
Oct 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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?
PlanModifierForASTConvoutside ofASTConverterand apply it explicitly inCalcitePlannergetOptimizedASTsince now it becomes a trivial callgetOptimizedASTWhy are the changes needed?
PlanModifierForASTConveffects inEXPLAIN CBOoutputDoes this PR introduce any user-facing change?
The output of
EXPLAIN CBOchanges slightly but there is no effect in correctness/performance cause the plan remains the same.How was this patch tested?
Existing tests