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

Posted to commits@hudi.apache.org by "ZiyueGuan (Jira)" <ji...@apache.org> on 2022/03/23 16:17:00 UTC

[jira] [Updated] (HUDI-3694) Not use magic number of next block to determine current log block

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

ZiyueGuan updated HUDI-3694:
----------------------------
    Description: HoodieLogFileReader use magic number of next log block to determine if current log block is corrupted. However, when next block has a corrupted magic number, we will abandon current block, which leads to data loss.  (was: HoodieLogFileReader use magic number of next log block to determine if current log block is corrupted. But when next is corrupted but current not. It will make it incorrect)

> Not use magic number of next block to determine current log block
> -----------------------------------------------------------------
>
>                 Key: HUDI-3694
>                 URL: https://issues.apache.org/jira/browse/HUDI-3694
>             Project: Apache Hudi
>          Issue Type: Bug
>            Reporter: ZiyueGuan
>            Priority: Major
>
> HoodieLogFileReader use magic number of next log block to determine if current log block is corrupted. However, when next block has a corrupted magic number, we will abandon current block, which leads to data loss.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)