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 "Kai Zheng (JIRA)" <ji...@apache.org> on 2015/08/17 09:17:45 UTC

[jira] [Updated] (HADOOP-12040) Adjust inputs order for the decode API in raw erasure coder

     [ https://issues.apache.org/jira/browse/HADOOP-12040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kai Zheng updated HADOOP-12040:
-------------------------------
    Attachment: HADOOP-12040-HDFS-7285-v1.patch

Uploaded the patch, ready for review.

> Adjust inputs order for the decode API in raw erasure coder
> -----------------------------------------------------------
>
>                 Key: HADOOP-12040
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12040
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Kai Zheng
>            Assignee: Kai Zheng
>             Fix For: HDFS-7285
>
>         Attachments: HADOOP-12040-HDFS-7285-v1.patch
>
>
> Currently we used the parity units + data units order for the inputs, erasedIndexes and outputs parameters in the decode call in raw erasure coder, which inherited from HDFS-RAID due to impact enforced by {{GaliosField}}. As [~zhz] pointed and [~hitliuyi] felt, we'd better change the order to make it natural for HDFS usage, where usually data blocks are before parity blocks in a group. Doing this would avoid some reordering tricky logic.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)