hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kai Zheng (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-12040) Adjust inputs order for the decode API in raw erasure coder
Date Fri, 29 May 2015 02:31:31 GMT
Kai Zheng created HADOOP-12040:
----------------------------------

             Summary: 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


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)

Mime
View raw message