hive-dev mailing list archives

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


Edward Capriolo commented on HIVE-2424:

I feel we are going to need them. I believe originally this was done because libjars was inconsistent
between hadoop version. However I do not think you can not take them out. Hive needs these
things to work. If you took them out from the hive-exec build and provided them with libjars
you would still end up with a conflict when adding your jars. (I could be wrong) 
> 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