HIVE-27516: Add programatically added DAG scoped properties to DAG Configuration #4503
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
abstractdog
force-pushed
the
HIVE-27516
branch
2 times, most recently
from
1060674 to
ec48479
Compare
kgyrtkirk
added
tests failed
tests pending
and removed
tests pending
tests failed
labels
abstractdog
changed the title
ayushtkn
approved these changes
Jul 20, 2023
Member
ayushtkn
left a comment
ayushtkn
left a comment
There was a problem hiding this comment.
LGTM, if the tests are green
|
Kudos, SonarCloud Quality Gate passed!
|
tarak271
pushed a commit
to tarak271/hive-1
that referenced
this pull request
Dec 19, 2023
…nfiguration (apache#4503) (Laszlo Bodor reviewed by Ayush Saxena)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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?
This change is about putting tez DAG scoped properties into DAG config while constructing the DAG,
Why are the changes needed?
Because without this patch, hive on tez user is unable to make tez options applied on dag level by simply doung set tez.x.y=z in beeline.
Does this PR introduce any user-facing change?
No.
Is the change a dependency upgrade?
No.
How was this patch tested?
Tested on cluster with TEZ-4344.