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 Wed, 04 Jul 2018 01:42:00 GMT


Alexander Kolbasov commented on HIVE-17751:

09.patch is merged with 

* commit e972122e0cad69a0a77110bb5ad11990b7bc5747 (origin/master, origin/HEAD, master)
| Author: Deepak Jaiswal <>
| Date:   Tue Jul 3 17:22:02 2018 -0700
|     HIVE-20039 : Bucket pruning: Left Outer Join on bucketed table gives wrong result (Deepak
Jaiswal, reviewed by Gopal V)

> 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,
HIVE-17751.06-standalone-metastore.patch, HIVE-17751.07.patch, HIVE-17751.08.patch, HIVE-17751.09.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