hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hairong Kuang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-7013) Add boolean field isCorrupt to BlockLocation
Date Tue, 16 Nov 2010 17:41:14 GMT

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

View raw message