HIVE-29217: Add configuration to choose materialization strategy for CTEs #6092
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
zabetak
force-pushed
the
cte-cbo-ast-procs
branch
from
3284f0b to
eb80d40
Compare
asf-ci-hive
added
tests pending
tests unstable
and removed
tests unstable
tests pending
labels
zabetak
force-pushed
the
cte-cbo-ast-procs
branch
from
eb80d40 to
8fc8884
Compare
asf-ci-hive
added
tests pending
tests unstable
and removed
tests unstable
tests pending
labels
zabetak
force-pushed
the
cte-cbo-ast-procs
branch
from
8fc8884 to
a7da724
Compare
|
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.
Why are the changes needed?
Avoid interference between AST and CBO based materialization of common table expressions (CTEs). More details in HIVE-29217.
Does this PR introduce any user-facing change?
Yes but highly unlikely. Users may see plan/perf changes if they set/rely on the experimental property
hive.optimize.cte.suggester.classand they expect both AST and CBO materialization to trigger sequentially one after the other.How was this patch tested?
Existing plus new tests.