hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Walter Su (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12040) Adjust inputs order for the decode API in raw erasure coder
Date Tue, 27 Oct 2015 09:15:27 GMT

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

Walter Su commented on HADOOP-12040:

Thanks [~drankye]! The v3 patch LGTM. (Non-binding)

> 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
>         Attachments: HADOOP-12040-HDFS-7285-v1.patch, HADOOP-12040-v2.patch, HADOOP-12040-v3.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

View raw message