[
https://issues.apache.org/jira/browse/HIVE-15419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763844#comment-15763844
]
Prasanth Jayachandran commented on HIVE-15419:
----------------------------------------------
Also I have concerns about overall turnaround time for a hive release.
Does this also mean storage-api release has to be released first, followed by
orc and then hive?
Can any two releases be squashed together? Trying to see if the turnaround time
can be reduced or the overall release process can be simplified.
> 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)
