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

Posted to issues@hive.apache.org by "Vihang Karajgaonkar (JIRA)" <ji...@apache.org> on 2017/10/10 04:07:02 UTC

[jira] [Assigned] (HIVE-17751) Separate HMS Client and HMS server into separate sub-modules

     [ https://issues.apache.org/jira/browse/HIVE-17751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vihang Karajgaonkar reassigned HIVE-17751:
------------------------------------------


> Separate HMS Client and HMS server into separate sub-modules
> ------------------------------------------------------------
>
>                 Key: HIVE-17751
>                 URL: https://issues.apache.org/jira/browse/HIVE-17751
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Vihang Karajgaonkar
>            Assignee: Vihang Karajgaonkar
>
> For external applications which are interfacing with HMS should ideally only include HMSClient library instead of one big library containing server as well. We should ideally have a thin client library so that cross version support for external applications is easier. We should sub-divide the standalone module into possibly 3 modules (one for common classes, one for client classes and one for server) or 2 sub-modules (one for client and one for server) so that we can generate separate jars for HMS client and server.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)