[
https://issues.apache.org/jira/browse/HIVE-17751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16522666#comment-16522666
]
Sergey Shelukhin commented on HIVE-17751:
-----------------------------------------
MM compactor and stats updater are both Hive query based, so they still require
Hive execution engine to run. I think there are tentative plans to move ACID
compactor in the same directions, for various benefits e.g. running on
Tez/LLAP, and some others that were discussed that I don't recall...
If everything is query based, we could have an interface to run the query that
would abstract this, but it would still basically require some Hive... it could
be embedded Hive (no HS2) running queries on Tez/MR that also don't require any
services being present; developing a non-query-based MM compactor (MM is not
tied to ORC so it has to support any formats and all that stuff) and stats
updater (same) seems like it's not worth the effort.
> 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.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
(v7.6.3#76005)
