hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Gates (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-20451) Metastore client and server tarball issues
Date Mon, 27 Aug 2018 20:43:00 GMT

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

Alan Gates commented on HIVE-20451:
-----------------------------------

The source tarball is what we actually release.  We need to be able to produce one "thing"
we release as the metastore, and the source tarball is it.

I'm confused because your comment seemed to indicate you want to keep two source tarballs,
but if I read the patch correctly you changed it to produce one source tarball from standalone-metastore,
as I suggested.  Am I missing something?

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

Mime
View raw message