You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Brock Noland (JIRA)" <ji...@apache.org> on 2013/11/05 06:19:17 UTC

[jira] [Commented] (HIVE-5725) Separate out ql code from exec jar

    [ https://issues.apache.org/jira/browse/HIVE-5725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813648#comment-13813648 ] 

Brock Noland commented on HIVE-5725:
------------------------------------

I'd propose we do away with the exec uber jar and utilize the libjars functionality to push the dependencies into the class path.

> Separate out ql code from exec jar
> ----------------------------------
>
>                 Key: HIVE-5725
>                 URL: https://issues.apache.org/jira/browse/HIVE-5725
>             Project: Hive
>          Issue Type: Bug
>          Components: Build Infrastructure
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>
> We should publish our code independently from our dependencies. Since the exec jar has to include the runtime dependencies, I'd propose that we make two jars, a ql jar and and exec jar.



--
This message was sent by Atlassian JIRA
(v6.1#6144)