hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Kling (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-7013) Add boolean field isCorrupt to BlockLocation
Date Wed, 17 Nov 2010 01:11:13 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932755#action_12932755

Patrick Kling commented on HADOOP-7013:

ant test-path results:
     [exec] -1 overall.  
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec]     -1 tests included.  The patch doesn't appear to include any new or modified
     [exec]                         Please justify why no new tests are needed for this patch.
     [exec]                         Also please list what manual steps were performed to verify
this patch.
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
     [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler
     [exec]     -1 findbugs.  The patch appears to introduce 2 new Findbugs warnings.
     [exec]     +1 release audit.  The applied patch does not increase the total number of
release audit warnings.
     [exec]     +1 system test framework.  The patch passed system test framework compile.

Tests are included with HDFS-1483. The findbugs warning are not caused by this patch (see
MAPREDUCE-2172 for details).

> Add boolean field isCorrupt to BlockLocation
> --------------------------------------------
>                 Key: HADOOP-7013
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7013
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Patrick Kling
>            Assignee: Patrick Kling
>         Attachments: HADOOP-7013.patch
> This is needed to allow DFSClient.getBlockLocations to notify the calling application
when returning a BlockLocation that corresponds to a corrupt block. Currently, this happens
when there are no uncorrupted replicas of a requested block.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message