[ 
https://issues.apache.org/jira/browse/MAPREDUCE-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tom White updated MAPREDUCE-3697:
---------------------------------

    Attachment: apicheck-hadoop-1.0.0-0.24.0-SNAPSHOT.sh

I reviewed the patch for compatibility with Hadoop 1.x. I ran a SigTest 
compatibility test (like in HADOOP-7738) to see what the differences between 
the mapred counters are between 1.0.0 and trunk with this patch (see attached). 
Most are false positives due to the inheritance hierarchy changing. Here are 
the ones that I think need fixing:

* Counters.getGroupNames returns an Iterable<String> not a Collection<String> 
as it does in 1.x. I think we should change it back to return 
Collection<String> - we can always add a getGroupNamesIterable() later if 
needed.
* method public java.lang.String 
org.apache.hadoop.mapred.Counters.makeCompactString() is missing
* public static int org.apache.hadoop.mapred.Counters.MAX_COUNTER_LIMIT is 
missing (it's not used in 23, but we should still define it for compatibility)
                
> Hadoop Counters API limits Oozie's working across different hadoop versions
> ---------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3697
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3697
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.1
>            Reporter: John George
>            Assignee: Mahadev konar
>            Priority: Blocker
>         Attachments: MAPREDUCE-3697-facade.patch, 
> MAPREDUCE-3697-facadeV2.patch, MAPREDUCE-3697-facadeV3.patch, 
> MAPREDUCE-3697.patch, MAPREDUCE-3697.patch, MAPREDUCE-3697.patch, 
> MAPREDUCE-3697.patch, MAPREDUCE-3697.patch, 
> apicheck-hadoop-1.0.0-0.24.0-SNAPSHOT.sh
>
>
> Oozie uses Hadoop Counters API, by invoking Counters.getGroup(). However, in
> hadoop 23, org.apache.hadoop.mapred.Counters does not implement getGroup(). 
> Its
> parent class AbstractCounters implements it. This is different from hadoop20X.
> As a result, Oozie compiled with either hadoop version does not work with the
> other version.
> A specific scenario, Oozie compiled with .23 and run against 205, does not
> update job status owing to a Counters API exception.
> Will explicit re-compilation against the relevant hadoop jars be required each
> time? This will prevent launching a uniform Oozie version across different
> clusters.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to