Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Tue, 20 Dec 2016 09:31:58 +0000 (UTC)
From: "Prasanth Jayachandran (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.13027561.1481571953000.561511.1482226318357@Atlassian.JIRA>
In-Reply-To: <JIRA.13027561.1481571953000@Atlassian.JIRA>
References: <JIRA.13027561.1481571953000@Atlassian.JIRA> <JIRA.13027561.1481571953287@arcas>
Subject: [jira] [Commented] (HIVE-15419) Separate out storage-api to be
 released independently
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 20 Dec 2016 09:32:00 -0000


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

Prasanth Jayachandran commented on HIVE-15419:
----------------------------------------------

From the proposal https://cwiki.apache.org/confluence/display/Hive/Storage+API+Release+Proposal
"Naturally, Hive releases can't refer to snapshot releases of Storage API and must use real releases. In the release branches of Hive, we'll change the Hive pom to refer to a specific release of Storage API and remove storage-api from the list of modules to be built."

I am still worried about Release Managers missing this part. Would it be possible do this via maven profile? Something similar to itests profile. Include the module during development by default and in release profile exclude the storage-api module, include storage-api dependency with latest release version.


> Separate out storage-api to be released independently
> -----------------------------------------------------
>
>                 Key: HIVE-15419
>                 URL: https://issues.apache.org/jira/browse/HIVE-15419
>             Project: Hive
>          Issue Type: Task
>          Components: storage-api
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>         Attachments: HIVE-15419.patch
>
>
> Currently, the Hive project releases a single monolithic release, but this makes file formats reading directly into Hive's vector row batches a circular dependence. Storage-api is a small module with the vectorized row batches and SearchArgument that are necessary for efficient vectorized read and write. By releasing storage-api independently, we can make an interface that the file formats can read and write from.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)