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 Tue, 03 Jul 2018 22:00:00 GMT


Alexander Kolbasov commented on HIVE-17751:

The new changes broke this pretty seriously - I need to spend some time to remerge.

[~alangates] [~vihangk1] I am running into a serious issue - there are a lot of upcoming changes
to metastore that almost always break me. This creates several problems:

* By the time my patch reaches ptest there is a conflicting change, so it can never merge
* I have to spend huge amount of time merging with upcoming changes
* It creates a high risk of mismerges - originally I just moved a lot of files and pieces
of files around, now I need to make sure that more recent commits are handled properly which
is error prone.

Alan - how did you handle similar issues for standalone metastore project? Would it be possible
to quiet down the change rate for the metastore?

> 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
> 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