hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3832) mapred Counters API should not extend mapreduce Counters API
Date Tue, 07 Feb 2012 17:54:59 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202571#comment-13202571

Mahadev konar commented on MAPREDUCE-3832:

 I am not sure I get the issue here. How does it affect backwards/forward compatibility?
> mapred Counters API should not extend mapreduce Counters API
> ------------------------------------------------------------
>                 Key: MAPREDUCE-3832
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3832
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.1
>            Reporter: Alejandro Abdelnur
>            Priority: Critical
> The mapred (old) Counters API extends the mapreduce (new) Counters API, this effectively
makes the old Counters API dependent on the new Counters API. This may affect stability and
backwards/forward compatibility in the old Counters API.
> The new API should not pop up as dependency in the old API. Instead it should only be
used in the implementation when necessary.

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


View raw message