You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Shuyan Zhang (Jira)" <ji...@apache.org> on 2024/08/19 04:48:00 UTC

[jira] [Resolved] (HADOOP-19180) EC: Fix calculation errors caused by special index order

     [ https://issues.apache.org/jira/browse/HADOOP-19180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shuyan Zhang resolved HADOOP-19180.
-----------------------------------
        Hadoop Flags: Reviewed
    Target Version/s: 3.5.0
          Resolution: Fixed

> 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-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org