You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Patrick Kling (JIRA)" <ji...@apache.org> on 2010/10/29 01:11:21 UTC

[jira] Created: (HADOOP-7013) Add boolean field isCorrupt to BlockLocation

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


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.

[jira] Resolved: (HADOOP-7013) Add boolean field isCorrupt to BlockLocation

Posted by "Hairong Kuang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-7013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hairong Kuang resolved HADOOP-7013.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.22.0
     Release Note: This patch has changed the serialization format of BlockLocation.
     Hadoop Flags: [Incompatible change, Reviewed]

I've just committed this. Thanks, Patrick!

> 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
>             Fix For: 0.22.0
>
>         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.