HIVE-29768: Fix ClassNotFoundException(SQLStdHiveAuthorizerFactoryForTest) in compactor tests - #6643
Open
maheshrajus wants to merge 1 commit into
Open
HIVE-29768: Fix ClassNotFoundException(SQLStdHiveAuthorizerFactoryForTest) in compactor tests#6643maheshrajus wants to merge 1 commit into
maheshrajus wants to merge 1 commit into
Conversation
…rTest) in compactor tests
|
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?
Disables
hive.compactor.gather.statsby default in the compactor test base class (CompactorTest)so post-compaction stats gathering no longer runs during unit tests.
These tests do not assert on the stats that StatsUpdater.gatherStats produces.
Why are the changes needed?
Every TestWorker run (and every other test extending CompactorTest) emits a loud stack trace(CNFE) after each successful compaction.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existed UT