[
https://issues.apache.org/jira/browse/HIVE-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262743#comment-13262743
]
Travis Crawford commented on HIVE-2424:
---------------------------------------
I think the root of the issue is hive-exec contains Hive classes that are
available in no other jar, plus the repackaged 3rd-party jars. This works great
for Hive itself, but presents integration issues if users need a different
3rd-party dependency for some reason. In an ideal world everyone would use the
same library versions, but since that's not always possible users may find
themselves in a situation where they need to change a library version.
hive-exec.jar contains all of the following Hive sub projects:
* hive-common
* hive-ql
* hive-serde
* hive-shims
What are your thoughts on publishing these four jars as stand-alone artifacts,
in addition to hive-exec. Since its strictly additive no existing behavior
would be affected. It would allow users writing tools on top of Hive to depend
on just the Hive classes, freeing them to construct their classpath as
appropriate for their site.
> Don't expose thrift, commons and json classes in the hive exec jar
> -------------------------------------------------------------------
>
> Key: HIVE-2424
> URL: https://issues.apache.org/jira/browse/HIVE-2424
> Project: Hive
> Issue Type: Improvement
> Components: Build Infrastructure
> Reporter: Eli Collins
>
> The hive exec jar includes exploded thrift, json, and commons lang classes.
> These may conflict with the user's classpath. This could be fixed by jar
> jaring or using shade. A mechanism that allowed a user to substitute
> alternative versions w/o recompiling might be a useful intermediate step
> (though will require the user substitute alternative versions that work w/
> Hive).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
