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

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha1
• Target Version/s: 2.8.0
• Hadoop Flags: Reviewed
• Assignee: Kai Zheng
• Reporter: Kai Zheng
• Created: 29/May/15 02:31
• Updated: 04/Jan/17 22:13
• Resolved: 28/Oct/15 08:31

Description

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.

Issue Links

• is depended upon by: HADOOP-11588 Benchmark framework and test for erasure coders
• is depended upon by: HADOOP-12041 Implement another Reed-Solomon coder in pure Java