[
https://issues.apache.org/jira/browse/HIVE-17751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16386489#comment-16386489
]
Vihang Karajgaonkar commented on HIVE-17751:
--------------------------------------------
I think hive-metastore-client should come under standalone-metastore module
along with metastore-common. Otherwise, projects other than Hive will have to
write their own HiveMetastoreClient (possible but they probably wont since that
may be too much work). Ideally, non-hive projects should only have
metastore-common and metastore-client jars in their classpaths to be able to
talk to metastore server. What are the maven issues you are running if you move
the client under standalone-metastore?
> 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
(v7.6.3#76005)
