[
https://issues.apache.org/jira/browse/OOZIE-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059166#comment-14059166
]
Robert Kanter commented on OOZIE-1586:
--------------------------------------
One thing to keep in mind is that Oozie is more tightly coupled to the
Hive/HCat version than it is to the other components. The others (e.g. Pig,
Sqoop, etc) are relatively easy to change versions assuming their clients are
backwards compatible. But because Oozie is now integrated with Hive/HCat, it
may become difficult to allow the user to use whatever version they want. I
suppose we could leave this as is, though it's an inconvenience for packaged
distros of Hadoop (Bigtop (BIGTOP-1349), CDH, HDP?) and users using Hive 13.1,
but I suppose the workaround is pretty easy, so I'm okay with leaving it as is
if you feel strongly about it. [~shwethags], do you feel strongly that we
should leave it as is?
{quote}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?{quote}
While this may work, it sounds very brittle. But I think this would be a
separate JIRA if we do this.
> 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)
