[
https://issues.apache.org/jira/browse/HADOOP-11646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350041#comment-14350041
]
Kai Zheng commented on HADOOP-11646:
------------------------------------
bq.{{isErased}}, Do you mean is block is missing and needs to re-construct?
Yes right. We have two cases, one is lost at all, the other is corrupt. I guess
both can be thought of as erased or bad due to erasure, and should consider
reconstruction. I updated the comment here.
bq.Why there are two separate methods with same params.
I'm thinking that there can be some common pre-checking and error handling
logic for all coder implementations in {{decode}} method before the call
{{performDecoding}}, though I don't have the codes for now.
For #3, #4, #5, #6, I followed and updated the codes accordingly. Thanks for
the great suggestions.
> Erasure Coder API for encoding and decoding of block group
> ----------------------------------------------------------
>
> Key: HADOOP-11646
> URL: https://issues.apache.org/jira/browse/HADOOP-11646
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Kai Zheng
> Assignee: Kai Zheng
> Fix For: HDFS-7285
>
> Attachments: HDFS-7662-v1.patch, HDFS-7662-v2.patch,
> HDFS-7662-v3.patch
>
>
> This is to define ErasureCoder API for encoding and decoding of BlockGroup.
> Given a BlockGroup, ErasureCoder extracts data chunks from the blocks and
> leverages RawErasureCoder defined in HDFS-7353 to perform concrete encoding
> or decoding.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
