Shaded commons-collections3.x in hive-exec jar for Tez-1.0.0 to prevent ClassNotFound Exception #6181
+1
−0
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
Contributor
Author
|
Error Stacktrace: |
Contributor
Author
|
In order to migrate from commons-collections3.x to 4.x in hive, few prerequisites are there:
|
|
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.
What changes were proposed in this pull request?
TEZ-4661 Include commons-collections3.x in hive-exec jar
Why are the changes needed?
In Tez-1.0.0-SNAPSHOT, hadoop has been upgraded to 3.4.2 and hadoop dependencies in tez project has stopped shipping commons-collections-3.x. But hive still depends on commons-collections3.x directly as well as thorugh third-party dependency like opencsv, commons-beanutils etc. It's better to shade until hive moves completely to commons-collection-4.x
Does this PR introduce any user-facing change?
No
How was this patch tested?
On local setup