[
https://issues.apache.org/jira/browse/HIVE-17751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517633#comment-16517633
]
Alexander Kolbasov commented on HIVE-17751:
-------------------------------------------
There is a new complication that was added recently.
HiveMetastoreClient now has this bit of code which is only used in embedded
mode:
{code}
MaterializationsInvalidationCache.get().init(conf, (IHMSHandler) client);
{code}
Both {{MaterializationsInvalidationCache}} and {{IHMSHandler}} do not belong to
either client or common code.
This was added as part of
HIVE-18776: MaterializationsInvalidationCache loading causes race condition in
the metastore (Jesus Camacho Rodriguez, reviewed by Alan Gates)
[~alangates] [~jcamachorodriguez] any thoughts how to handle this case for
standalone client?
I am using reflection to initialize standalone client, but in this case it
seems rather tricky.
> 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)
