hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Kolbasov (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HIVE-20451) Metastore client and server tarball issues
Date Tue, 28 Aug 2018 21:55:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-20451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16595648#comment-16595648
] 

Alexander Kolbasov edited comment on HIVE-20451 at 8/28/18 9:54 PM:
--------------------------------------------------------------------

Posted an updated patch that seems a bit cleaner. Here is what it does.

# Only one binary tarball is generated in metastore-server target directory. It is called
{{apache-hive-standalone-metastore-server-4.0.0-SNAPSHOT-bin.tar.gz}}. I don't think that
we need binary tarbal for the metastore-common - there are no binaries to run from there.
# {{standalone-metastore/target}} has the overall tarball called {{apache-hive-standalone-metastore-4.0.0-SNAPSHOT-src.tar.gz}}
which includes full source and can be used to build standalone metastore.
# submodules have their own source tarballs that can be used to build these submodules. They
all have different names. I don't know how the release process works, but basically it may
choose to exclude these from the release. 

Is this an acceptable state of affairs?


was (Author: akolb):
Posted an updated patch that seems a bit cleaner. Here is what it does.

# Only one binary tarball is generated in metastore-server target directory. It is called
{{apache-hive-standalone-metastore-server-4.0.0-SNAPSHOT-bin.tar.gz}}. I don't think that
we need binary tarbal for the metastore-common - there are no binaries to run from there.
# {{standalone-metastore/target}} has the overall tarball called {{apache-hive-standalone-metastore-4.0.0-SNAPSHOT-src.tar.gz
}} which includes full source and can be used to build standalone metastore.
# submodules have their own source tarballs that can be used to build these submodules. They
all have different names. I don't know how the release process works, but basically it may
choose to exclude these from the release. 

Is this an acceptable state of affairs?

> 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, HIVE-20451.02.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)

Mime
View raw message