[
https://issues.apache.org/jira/browse/HIVE-20451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16592321#comment-16592321
]
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}} file
# {{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: https://issues.apache.org/jira/browse/HIVE-20451
> 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 metastore.
> # The binary tarballs should have separate names. At the moment both are
> named apache-hive-metastore.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
