hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4875) coverage fixing for org.apache.hadoop.mapred
Date Wed, 20 Mar 2013 14:43:16 GMT

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

Jason Lowe commented on MAPREDUCE-4875:

Any publicly visible methods for externally visible classes are going to be off-limits for
removal.  For example, JobClient is marked Public and Stable.  Even though nothing in Apache
Hadoop may be calling JobClient#getQueues now, there could easily be external code built on
top it that is.  Deprecated methods are a gray area, as they are effectively marked for removal
at some point, but I don't think the charter of this JIRA should be to remove public deprecated
methods.  A separate JIRA specifically for removing deprecated methods would be more appropriate,
as it would be clear in the list of changes for a release and users could easily take notice.

Classes marked Private, like TaskLog, are probably OK for removing dead methods since they
are not supposed to be part of the public interface.
> coverage fixing for org.apache.hadoop.mapred
> --------------------------------------------
>                 Key: MAPREDUCE-4875
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4875
>             Project: Hadoop Map/Reduce
>          Issue Type: Test
>          Components: test
>    Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6
>            Reporter: Aleksey Gorshkov
>             Fix For: 3.0.0, 0.23.6, 2.0.5-beta
>         Attachments: MAPREDUCE-4875-branch-0.23.patch, MAPREDUCE-4875-trunk.patch
> added  some tests for org.apache.hadoop.mapred
> MAPREDUCE-4875-trunk.patch for trunk and branch-2
> MAPREDUCE-4875-branch-0.23.patch for branch-0.23

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message