You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "Danny Chen (Jira)" <ji...@apache.org> on 2021/08/12 09:17:00 UTC

[jira] [Updated] (HUDI-2299) The log format DELETE block lose the info orderingVal

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

Danny Chen updated HUDI-2299:
-----------------------------
    Fix Version/s:     (was: 0.9.0)
                   0.10.0

> The log format DELETE block lose the info orderingVal
> -----------------------------------------------------
>
>                 Key: HUDI-2299
>                 URL: https://issues.apache.org/jira/browse/HUDI-2299
>             Project: Apache Hudi
>          Issue Type: Bug
>          Components: Common Core
>            Reporter: Danny Chen
>            Priority: Major
>             Fix For: 0.10.0
>
>
> The append handle now always write data block first then delete block, and the delete block only keeps the hoodie keys, when reading, the scanner just read the DELETE block without any info of ordering value, thus, if the we write two records:
> insert: {id: 0, ts: 2}
> delete: {id: 0, ts: 1}
> Finally the insert message is deleted !!!, this is a critical bug for streaming write, we should fix it as soon as possible



--
This message was sent by Atlassian Jira
(v8.3.4#803005)