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