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

Posted to commits@hudi.apache.org by "sivabalan narayanan (Jira)" <ji...@apache.org> on 2023/04/30 18:16:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17718089#comment-17718089 ] 

sivabalan narayanan commented on HUDI-3694:
-------------------------------------------

This might potentially be an issue only for hdfs like storage schemes where appends are feasible. 

> 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.10#820010)