[
https://issues.apache.org/jira/browse/OOZIE-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058441#comment-14058441
]
Shwetha G S commented on OOZIE-1586:
------------------------------------
[~rkanter], I understand that bundling hcat jars makes the oozie installation
simpler. My concern is that in future, with new versions of hive, what if the
bundled hive jars are not compatible with the installed hive version(thats a
possibility)? How will the user inject custom versioned hive jars with the new
approach?
Is separate oozie-setup command used? Why can't it be part of oozie-start
itself? If oozie-setup and oozie-start were one command, we could bundle
default hcat jars as separate directory in oozie package, and oozie-start can
check if hcat jars are available in libext, else include default hcat jars(also
print hcat version the oozie is started with). That could work?
> upgrade oozie to hive 13.1 (including hcatalog)
> -----------------------------------------------
>
> Key: OOZIE-1586
> URL: https://issues.apache.org/jira/browse/OOZIE-1586
> Project: Oozie
> Issue Type: Improvement
> Reporter: Bowen Zhang
> Assignee: Ravi Prakash
> Attachments: OOZIE-1586.1.patch, OOZIE-1586.2.patch,
> OOZIE-1586.3.patch, OOZIE-1586.4.patch, OOZIE-1586.5.patch, OOZIE-1586.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
