[ https://issues.apache.org/jira/browse/HADOOP-19180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17847240#comment-17847240 ]
ASF GitHub Bot commented on HADOOP-19180: ----------------------------------------- zhengchenyu commented on PR #6813: URL: https://github.com/apache/hadoop/pull/6813#issuecomment-2117347235 The reported error "Doesn't support SM4 CTR." seems to be not related to this PR. Perhaps the compiler environment has changed? > EC: Fix calculation errors caused by special index order > -------------------------------------------------------- > > Key: HADOOP-19180 > URL: https://issues.apache.org/jira/browse/HADOOP-19180 > Project: Hadoop Common > Issue Type: Bug > Reporter: Chenyu Zheng > Assignee: Chenyu Zheng > Priority: Critical > Labels: pull-request-available > > I found that if the erasedIndexes distribution is such that the parity index > is in front of the data index, ec will produce wrong results when decoding. > In fact, HDFS-15186 has described this problem, but does not fundamentally > solve it. > The reason is that the code assumes that erasedIndexes is preceded by the > data index and followed by parity index. If there is a parity index placed in > front of the data index, a calculation error will occur. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org