[
https://issues.apache.org/jira/browse/HIVE-26220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534713#comment-17534713
]
Zoltan Haindrich commented on HIVE-26220:
-----------------------------------------
[~csun] have you tried using the current hive-exec from master?
the shading was improved some time ago; especially in HIVE-22126.
Probably the best would be to provide some usecases for the usage of the
artifact - preferably with testcases; so that we don't break it again in the
future...but I admit - this might not be a good ask...
Correct me if I'm wrong but it sounds a bit unfair to push the task of
evaluating and upgrading other projects to run with the next version - just
because they might upgrade to it (in my mind fixing this blocker task would
mean that).
So I think the best middle ground could be to provide support for projects
which do "their part" first - and they could link some development branches
which is already using an 4.0.0-alpha-X release.
> Shade & relocate dependencies in hive-exec to avoid conflicting with
> downstream projects
> ----------------------------------------------------------------------------------------
>
> Key: HIVE-26220
> URL: https://issues.apache.org/jira/browse/HIVE-26220
> Project: Hive
> Issue Type: Improvement
> Affects Versions: 4.0.0
> Reporter: Chao Sun
> Priority: Blocker
>
> Currently projects like Spark, Trino/Presto, Iceberg, etc, are depending on
> {{hive-exec:core}} which was removed in HIVE-25531. The reason these projects
> use {{hive-exec:core}} is because they have the flexibility to exclude, shade
> & relocate dependencies in {{hive-exec}} that conflict with the ones they
> brought in by themselves. However, with {{hive-exec}} this is no longer
> possible, since it is a fat jar that shade those dependencies but do not
> relocate many of them.
> In order for the downstream projects to consume {{hive-exec}}, we will need
> to make sure all the dependencies in {{hive-exec}} are properly shaded and
> relocated, so they won't cause conflicts with those from the downstream.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
