You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Hairong Kuang (JIRA)" <ji...@apache.org> on 2010/11/16 18:41:14 UTC

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

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

Hairong Kuang commented on HADOOP-7013:
---------------------------------------

The patch looks good except for an incompatible change.

BlockLocation is not used in any wire-protocol, but for some reason it is Writable. So if by any chance somebody serialize this object in a file etc, then this patch makes it incompatible.

I would suggest that this patch does not change the serialization format. Since Hadoop does not use it over the wire, it won't do any harm.

> 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
>         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.