hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Travis Crawford (JIRA)" <>
Subject [jira] [Commented] (HIVE-2424) Don't expose thrift, commons and json classes in the hive exec jar
Date Thu, 26 Apr 2012 23:00:49 GMT


Travis Crawford commented on HIVE-2424:

Possibly jarjar/shade will solve the problem - I'm not familiar with how they work and will
take a look.

Your point to user confusion about the new jars is definitely valid. Its a trade-off though,
since there's existing confusion about how to work around hive-exec. Likely most users will
just install a release and not be bothered by these additional jars. Developers integrating
with Hive would likely benefit from being able to construct a custom classpath.

The posted approach does add an extra sub project & build files, but maintenance overhead
is pretty small since mostly they inherit {{build-common.xml}} functionality. Perhaps I could
offset the additional overhead by simplifying the maven-related tasks in {{build.xml}}? There's
some repetitiveness that could be simplified with macros & other minor restructuring.

I'll take a look at jarjar and see if that easily solves this issue.
> Don't expose thrift, commons and json classes in the hive exec jar 
> -------------------------------------------------------------------
>                 Key: HIVE-2424
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message