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 22:03:14 GMT

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

Hairong Kuang commented on HADOOP-7013:

On a second thought, Hadoop does not have a story for Writable backward compatibility yet.
So this patch does not need to take care of this either. Instead we could simply mark this
jira as incompatible.

So a +1 from me.

> 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