hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <>
Subject [jira] [Commented] (HIVE-17751) Separate HMS Client and HMS server into separate sub-modules
Date Fri, 22 Jun 2018 18:20:00 GMT


Sergey Shelukhin commented on HIVE-17751:

Hmm... it depends on metastore plans as a separate project. Stats updater and ACID compactor
both run Hive queries but live in metastore.
If they are going to stay in metastore it might make sense to have an abstraction for server
to depend on for that purpose, when used with Hive... I don't think they depend on anything
else in ql.
Otherwise if the plan is to move them to Hive side (hosted in e.g. HS2) it won't be a problem.

> Separate HMS Client and HMS server into separate sub-modules
> ------------------------------------------------------------
>                 Key: HIVE-17751
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Standalone Metastore
>            Reporter: Vihang Karajgaonkar
>            Assignee: Alexander Kolbasov
>            Priority: Major
>         Attachments: HIVE-17751.01.patch, 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

View raw message