[
https://issues.apache.org/jira/browse/HIVE-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262898#comment-13262898
]
Travis Crawford commented on HIVE-2424:
---------------------------------------
To make the discussion a bit more concrete, I went ahead and experimented with
publishing subproject jars in addition to the existing fat jar.
Check out the following branch where I created a new "exec" subproject that
produces hive-exec.jar, and where "ql" produces a hive-ql.jar like other sub
projects.
https://github.com/traviscrawford/hive/compare/HIVE-2424_thin_jars
What do y'all think about this approach? It would let existing stuff continue
working as-is, while making all Hive classes available for those that for
whatever reason need to do something fancy.
Thoughts?
> 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
