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

Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2016/01/27 23:03:40 UTC

[jira] [Commented] (HIVE-12934) Refactor llap module structure to allow for a usable client

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

Sergey Shelukhin commented on HIVE-12934:
-----------------------------------------

Can you please verify packaging and running from scratch somewhere? 
Also do llap-server/src/main/resources/META-INF/services/ files need to be changed? Not as far as I see.
Was protocol class fully renamed or split into 2? It seems like it was renamed, so it should be ok, if it was split, the secure setup needs to be verified as it depends on protocol classes.

> Refactor llap module structure to allow for a usable client
> -----------------------------------------------------------
>
>                 Key: HIVE-12934
>                 URL: https://issues.apache.org/jira/browse/HIVE-12934
>             Project: Hive
>          Issue Type: Task
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>         Attachments: HIVE-12934.1.patch, HIVE-12934.1.review.txt, HIVE-12934.1.txt
>
>
> The client isn't really usable at the moment, and all of the code resides in the llap-server module. Restructure this so that the daemon execution code and cache code remains in server, common components move to a different module and relevant client pieces sit in the client module.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)