[
https://issues.apache.org/jira/browse/HIVE-20483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16612866#comment-16612866
]
Alexander Kolbasov commented on HIVE-20483:
-------------------------------------------
[~ngangam]
The goal is to have the following structure:
# hive-metastore-server contains everything needed for the metastore server
itself. Nothing there should be needed for clients (unless they use embedded
metastore.
# hive-metastore-common contains shared code that is used by both client and
server
# The plan is to introduce hive-metastore-client module later which will have
everything needed to have a metastore client, but it isn't done yet, so for now
every client should just use hive-metastore-common
All the classes that I moved into common are used outside of metastore server
one way or another. The goal is to untangle all such dependencies eventually
but for now all such classes just live in hive-metastore-common and will be
required for the client as well.
> Really move metastore common classes into metastore-common
> ----------------------------------------------------------
>
> Key: HIVE-20483
> URL: https://issues.apache.org/jira/browse/HIVE-20483
> Project: Hive
> Issue Type: Sub-task
> Components: Standalone Metastore
> Affects Versions: 3.0.1, 4.0.0
> Reporter: Alexander Kolbasov
> Assignee: Alexander Kolbasov
> Priority: Major
> Attachments: HIVE-20483.01.patch, HIVE-20483.02.patch,
> HIVE-20483.03.patch, HIVE-20483.04.patch, HIVE-20483.05.patch,
> HIVE-20483.06.patch
>
>
> HIVE-20388 patch was supposed to move a bunch of files from metastore-server
> to metastore-common but for some reason it didn't happen, so now these files
> should be moved.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)