You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Alexander Kolbasov (JIRA)" <ji...@apache.org> on 2019/01/16 02:46:00 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 ]

Alexander Kolbasov reassigned HIVE-17751:
-----------------------------------------

    Assignee: Peter Vary  (was: Alexander Kolbasov)

> 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: Improvement
>          Components: Standalone Metastore
>            Reporter: Vihang Karajgaonkar
>            Assignee: Peter Vary
>            Priority: Major
>         Attachments: HIVE-17751.01.patch, HIVE-17751.02.patch, HIVE-17751.03.patch, HIVE-17751.04.patch, HIVE-17751.07.patch, HIVE-17751.08.patch, HIVE-17751.09.patch, HIVE-17751.10.patch, HIVE-17751.11.patch, HIVE-17751.13.patch, HIVE-17751.14.patch, HIVE-17751.15.patch
>
>
> 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
(v7.6.3#76005)