[
https://issues.apache.org/jira/browse/HIVE-17751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16321540#comment-16321540
]
Alexander Kolbasov edited comment on HIVE-17751 at 1/11/18 1:48 AM:
--------------------------------------------------------------------
MetastoreClient has a "feature" - when metastore URI is not specified, it
instantiates embedded metastore which immediately brings the dependency on
standalone metastore to the client code. It can be disabled by caller.
I think it is a wrong idea to use the client class to instantiate embedded
metastore, but I don't know how deep this thing is in the guts of everything.
Any thoughts on this?
was (Author: akolb):
MetastoreClient has a "feature" - when metastore URI is not specified, it
instantiates embedded metastore which immediately brings the dependency on
standalone metastore to the client code. It can be disabled by caller.
I think it is a wrong idea to use the client class to instantiate embedded
metastore, but I don't know how deep this thing is tn the guts of everything.
Any thoughts on this?
> 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: Vihang Karajgaonkar
>
> 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)
