You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Shwetha G S (JIRA)" <ji...@apache.org> on 2015/07/28 12:12:04 UTC

[jira] [Commented] (OOZIE-2316) Drop support for Hadoop 1 and 0.23

    [ https://issues.apache.org/jira/browse/OOZIE-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644175#comment-14644175 ] 

Shwetha G S commented on OOZIE-2316:
------------------------------------

+1, it will simplify the build for some dependent projects like falcon

> Drop support for Hadoop 1 and 0.23
> ----------------------------------
>
>                 Key: OOZIE-2316
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2316
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: trunk
>            Reporter: Robert Kanter
>
> Given that Hadoop 2.x has had many releases now (2.8 is next), Hadoop 1.x hasn't had a release in a really long time, and Hadoop 3.0 is coming somewhat soonish, it would be good to drop support Hadoop 1.x and Hadoop 0.23.  I believe most users are using Hadoop 2.x anyway.
> This should help simplify the build a lot as we can probably get rid of the hadooplibs stuff and don't need to set Hadoop 1 and Hadoop 2+ properties (e.g. JT and RM addresses), so we can get rid of those cases as well.
> It might also be good to create new versions of the schemas that use {{<resource-manager>}} instead of {{<job-tracker>}} (the existing schemas would of course still work).  While this is a minor thing, it does bring up questions every so often of "does Oozie support Hadoop 2/YARN?"  And "how do I specify the RM?"  Alternatively, we could update the existing schemas to allow one of {{<resource-manager>}} or {{<job-tracker>}}.  I'm not sure what we should do about any config properties in Oozie site that mention "job-tracker".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)