hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Kolbasov (JIRA)" <>
Subject [jira] [Commented] (HIVE-20451) Metastore client and server tarball issues
Date Fri, 24 Aug 2018 23:52:00 GMT


Alexander Kolbasov commented on HIVE-20451:

With this patch I have the following result:

# {{standalone-metastore/target}} has the full source called {{ apache-hive-metastore-4.0.0-SNAPSHOT-src.tar.gz}}
# {{standalone-metastore/metastore-server/target}} has {{apache-hive-metastore--server-4.0.0-SNAPSHOT-bin.tar.gz}}
# {{standalone-metastpre/metastore-common/target}} has {{apache-hive-metastore-4.0.0-SNAPSHOT-src.tar.gz}}

I don't think we need a binary tarball for metastore-common because there is nothing that
can be executed from there.
I tried to eliminate source tarball from metastore-common but it is still created because
top-level now defines assembly plugin which is inherited by metastore-common. Is it really
a problem?

> Metastore client and server tarball issues
> ------------------------------------------
>                 Key: HIVE-20451
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Standalone Metastore
>    Affects Versions: 4.0.0
>            Reporter: Alan Gates
>            Assignee: Alexander Kolbasov
>            Priority: Major
>         Attachments: HIVE-20451.01.patch
> With the split of the metastore into common and server there are now two sets of tarballs. 
There are a couple of issues here.
>  # It doesn't make sense to have separate source tarballs for each.  The source release
should still be done from the standalone-metastore directory and include all code for the
>  # The binary tarballs should have separate names.  At the moment both are named apache-hive-metastore.

This message was sent by Atlassian JIRA

View raw message