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] [Commented] (HIVE-20451) Metastore client and server tarball issues
Date Fri, 24 Aug 2018 23:59:00 GMT

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

Alexander Kolbasov commented on HIVE-20451:
-------------------------------------------

[~alangates] IMO it is a bit cleaner to split source tarballs into common and server. This
eliminates any actual maven executions at the standalone-metastore level that cause troubles
when they are inherited. Is there an issue with having two separate source tarballs?

What is the use case for source tarballs?


> 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