hive-dev mailing list archives

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


Carl Steinbach commented on HIVE-2424:

There's a Thrift dependency on the MR classpath because we use Thrift to serialize the query
plan. As for the other dependencies, json and commons-lang are both required by a bunch of
UDFs, and javaewah is required by the UDFs that generate bitmap indexes.

I don't think there's going to be much support for splitting these out into separate JARs
because it increases the chances of jobs failing due to unsatisfied dependencies.

@Travis: Any chance you'd be willing to investigate the JarJar approach?

> 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