You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2011/08/04 05:43:27 UTC
[jira] [Updated] (MAPREDUCE-2773) [MR-279]
server.api.records.NodeHealthStatus renamed but not updated in client
NodeHealthStatus.java
[ https://issues.apache.org/jira/browse/MAPREDUCE-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli updated MAPREDUCE-2773:
-----------------------------------------------
Summary: [MR-279] server.api.records.NodeHealthStatus renamed but not updated in client NodeHealthStatus.java (was: mr279 server.api.records.NodeHealthStatus renamed but not updated in client NodeHealthStatus.java)
Thanks Thomas! I caused this bug - one that escaped in those multitude of commits. Thanks for covering me ;)
> [MR-279] server.api.records.NodeHealthStatus renamed but not updated in client NodeHealthStatus.java
> ----------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-2773
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2773
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Thomas Graves
> Assignee: Thomas Graves
> Priority: Minor
> Fix For: 0.23.0
>
> Attachments: nodehealth.patch
>
>
> On the mr279 branch, you can't successfully run the ant target from the mapreduce directory since the checkin of the RM refactor.
> The issue is the NodeHealthStatus rename from org.apache.hadoop.yarn.server.api.records.NodeHealthStatus to org.apache.hadoop.yarn.api.records.NodeHealthStatus but the client mapreduce/src/java/org/apache/hadoop/mapred/NodeHealthStatus.java wasn't updated with the change
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira