[
https://issues.apache.org/jira/browse/HIVE-17751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16535943#comment-16535943
]
Alexander Kolbasov commented on HIVE-17751:
-------------------------------------------
Patch 14 merged with
{code}
* commit 406cde9883a0a9f2d740c8c9e0104b5c06a4fbff (origin/master, origin/HEAD,
master)
| Author: Nishant Bangarwa <[email protected]>
| Date: Sat Jul 7 09:22:17 2018 -0700
|
| HIVE-20085 : Druid-Hive (managed) table creation fails with strict
managed table checks: Table is marked as a managed table but is not
transactional (Nishant Bangarwa via Ashutosh Chauhan)
{code}
> 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: Improvement
> Components: Standalone Metastore
> Reporter: Vihang Karajgaonkar
> Assignee: Alexander Kolbasov
> Priority: Major
> Attachments: HIVE-17751.01.patch, HIVE-17751.02.patch,
> HIVE-17751.03.patch, HIVE-17751.04.patch,
> HIVE-17751.06-standalone-metastore.patch, HIVE-17751.07.patch,
> HIVE-17751.08.patch, HIVE-17751.09.patch, HIVE-17751.10.patch,
> HIVE-17751.11.patch, HIVE-17751.13.patch, HIVE-17751.14.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)
