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

Hadoop QA commented on OOZIE-2316:
----------------------------------

Testing JIRA OOZIE-2316

Cleaning local git workspace

----------------------------

{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.    {color:green}+1{color} the patch does not introduce any @author tags
.    {color:green}+1{color} the patch does not introduce any tabs
.    {color:green}+1{color} the patch does not introduce any trailing spaces
.    {color:red}-1{color} the patch contains 1 line(s) longer than 132 
characters
.    {color:green}+1{color} the patch does adds/modifies 10 testcase(s)
{color:green}+1 RAT{color}
.    {color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:red}-1 COMPILE{color}
.    {color:green}+1{color} HEAD compiles
.    {color:red}-1{color} patch does not compile
.    {color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.    {color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.    {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:red}-1 DISTRO{color}
.    {color:red}-1{color} distro tarball fails with the patch

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/2983/

> 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, oya
>            Reporter: Robert Kanter
>            Assignee: Attila Sasvari
>         Attachments: OOZIE-2316-001.patch, OOZIE-2316-002.patch, 
> OOZIE-2316-003.patch, OOZIE-2316-004.patch, OOZIE-2316-005.patch
>
>
> 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)

Reply via email to