hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12040) Adjust inputs order for the decode API in raw erasure coder
Date Wed, 04 Jan 2017 22:13:58 GMT

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

Junping Du commented on HADOOP-12040:

I believe this patch went only to trunk. Remove 2.8 from fix version.

> 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: 3.0.0-alpha1
>         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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message