[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-v2.patch Rebased the patch on trunk. > 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, HADOOP-12040-v2.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)
[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: --- Fix Version/s: (was: HDFS-7285) > 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 > > > 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)
[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-v3.patch Updated the patch addressing the found checking style issues. Failed tests were not related. > 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 (v6.3.4#6332)
[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-v4.patch Thanks Yi for the clarifying! Updated the patch addressed the check style issues. Also double checked related unit tests. > 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, HADOOP-12040-v4.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)
[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 ] Yi Liu updated HADOOP-12040: Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.8.0 Target Version/s: 2.8.0 Status: Resolved (was: Patch Available) Committed to trunk and branch-2. > 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: 2.8.0 > > Attachments: HADOOP-12040-HDFS-7285-v1.patch, HADOOP-12040-v2.patch, > HADOOP-12040-v3.patch, HADOOP-12040-v4.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)
[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 ] Junping Du updated HADOOP-12040: Fix Version/s: (was: 2.8.0) > 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, HADOOP-12040-v4.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) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[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)
[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: --- Fix Version/s: HDFS-7285 Status: Patch Available (was: Open) > 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)