[
https://issues.apache.org/jira/browse/HIVE-6593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924684#comment-13924684
]
Prasad Mujumdar commented on HIVE-6593:
---------------------------------------
[~szehon] Thanks for picking it up.
I would suggest not to worry about bigtop side. Their ask is to create a JDBC
tarball that they can use as is to create packages. We need to make sure all
the dependent jars and other files (if any) required for JDBC client are part
of the tarball.
> Create a maven assembly for hive-jdbc
> -------------------------------------
>
> Key: HIVE-6593
> URL: https://issues.apache.org/jira/browse/HIVE-6593
> Project: Hive
> Issue Type: Improvement
> Components: Build Infrastructure
> Affects Versions: 0.12.0
> Reporter: Mark Grover
> Assignee: Szehon Ho
>
> Currently in Apache Bigtop we bundle and distribute Hive. In particular, for
> users to not have to install the entirety of Hive on machines that are just
> jdbc clients, we have a special package which is a subset of hive, called
> hive-jdbc that bundles only the jdbc driver jar and it's dependencies.
> However, because Hive doesn't have an assembly for the jdbc jar, we have to
> hack and hardcode the list of jdbc jars and it's dependencies:
> https://github.com/apache/bigtop/blob/master/bigtop-packages/src/rpm/hive/SPECS/hive.spec#L361
> As Hive moves to Maven, it would be pretty fantastic if Hive could leverage
> the maven-assembly-plugin and generate a .tar.gz assembly for what's required
> for jdbc gateway machines. That we can simply take that distribution and
> build a jdbc package from it without having to hard code jar names and
> dependencies. That would make the process much less error prone.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
