hadoop-mapreduce-issues mailing list archives

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

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

Mahadev konar updated MAPREDUCE-3832:
-------------------------------------

    Priority: Major  (was: Critical)

Downgrading this to major. This would be a good thing to have but I dont think we need it
right now. Running jdiff should give us enough warning on this.
                
> 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
>
> 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

        

Mime
View raw message