HIVE-29490: Add tests for HIVE-26758 (hive.use.scratchdir.for.staging)#6562
Open
maheshrajus wants to merge 2 commits into
Open
HIVE-29490: Add tests for HIVE-26758 (hive.use.scratchdir.for.staging)#6562maheshrajus wants to merge 2 commits into
maheshrajus wants to merge 2 commits into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
HIVE-26758[PR: https://github.com//pull/3831] added the
hive.use.scratchdir.for.stagingconfiguration and changed the dynamic-partition staging directory layout for native, non-MM, non-direct-insert tables.However, no automated tests were added along with that change. This PR adds the missing test coverage for those changes.
Why are the changes needed?
This PR adds the missing unit and end-to-end test coverage to protect the correctness of the HIVE-26758 implementation.
Does this PR introduce any user-facing change?
No
How was this patch tested?
UT and qtest