HIVE-29107: Drop avatica version management and use of shaded jars #5984
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?
Avatica is tightly connected with Calcite so it doesn't make sense to manage it separately Moreover, there is no need to use the shaded avatica artifact since the latter pulls in tons of things that Hive doesn't need.
Does this PR introduce any user-facing change?
No product facing changes for Hive users.
However, due to the removal of the shaded avatica jar some classes will not be part hive-exec so maven projects that depend on hive-exec may run into
ClassNotFoundException
issues if they depend implicitly on code bundled in avatica.How was this patch tested?