Alexander Kolbasov commented on HIVE-17751:

My initial approach was for have hive-metastore-common and 
hive-metastore-client live as submodules of top-level Hive. [~pvary] suggested 
to move these modules in standalone-metastore and now I am running into weird 
maven dependency issues. [~alangates] [~vihangk1] - where do you thing is the 
right location for

1) Common code shared between hive-standalone-metastore and Hive needed for the 
2) Actual implementation of hive metastore client

> 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
>          Components: Standalone Metastore
>            Reporter: Vihang Karajgaonkar
>            Assignee: Alexander Kolbasov
>            Priority: Major
>         Attachments: HIVE-17751.06-standalone-metastore.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

Reply via email to