[
https://issues.apache.org/jira/browse/HIVE-14069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16234632#comment-16234632
]
Jason Dere commented on HIVE-14069:
-----------------------------------
Trying to go with the shading approach - shading within each Hive module that
uses Curator.
One issue I have been running into is MSHADE-148. The maven-shade plugin
normally tries to generate a new POM file which does not include any of the
shaded dependencies, which should be a good thing because (1) we don't want the
conflicting Curator versions from Hadoop and Hive being brought into the
classpath together, and (2) since the Curator version used by Hive would be
shaded, there is no need to bring it into the classpath. Unfortunately
MSHADE-148 is causing some kind of infinite loop when generating this new
dependency-reduced POM file. We can disable this POM generation step in the
shade options, but then this means the original POM file for the Hive module is
being used which specifies the new Curator version as a dependency. Thinking we
can set the Curator dependencies as optional dependencies in maven so they do
not get brought into the classpath as transitive dependencies.
> update curator version to 2.10.0
> ---------------------------------
>
> Key: HIVE-14069
> URL: https://issues.apache.org/jira/browse/HIVE-14069
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2, Metastore
> Reporter: Thejas M Nair
> Assignee: Jason Dere
> Priority: Major
> Attachments: HIVE-14069.1.patch
>
>
> curator-2.10.0 has several bug fixes over current version (2.6.0), updating
> would help improve stability.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
