hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Kolbasov (JIRA)" <>
Subject [jira] [Commented] (HIVE-17751) Separate HMS Client and HMS server into separate sub-modules
Date Sun, 01 Jul 2018 21:59:00 GMT


Alexander Kolbasov commented on HIVE-17751:

We have a problem with this patch - it is huge and touches many files. By the time it reaches
the slot in the test queue, someone commits a conflicting code and the patch fails to merge.

patch.04 is applied on top of 

* commit 455b71e4a2a51838818b77786566297b1fabb233 (origin/master, origin/HEAD)
| Author: Peter Vary <>
| Date:   Sun Jul 1 22:27:37 2018 +0200
|     HIVE-20034: Roll back MetaStore exception handling changes for backward compatibility
(Peter Vary, reviewed by Sergey Shelukhin)

> 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.02.patch, HIVE-17751.03.patch, HIVE-17751.04.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