[
https://issues.apache.org/jira/browse/HIVE-15419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767865#comment-15767865
]
Owen O'Malley commented on HIVE-15419:
--------------------------------------
Generally, we should release storage-api and ORC when they are ready, so they
shouldn't be gates on getting the Hive release. Let's take the fast decimal
patch, for example, we would release a new version of storage-api and ORC that
incorporates that change.
If a last minute bug fix comes in that is blocking the Hive release, we could
hold the three votes concurrently with the votes being contingent on each
other. If the storage-api vote fails, you want the vote for ORC and Hive to
fail also.
> 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)
