[jira] [Assigned] (HUDI-5432) Fix adding back a log block w/ same commit time as previously rolled back one

["sivabalan narayanan (Jira)" <ji...@apache.org>]

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

sivabalan narayanan reassigned HUDI-5432:
-----------------------------------------

    Assignee: Raymond Xu

> Fix adding back a log block w/ same commit time as previously rolled back one
> -----------------------------------------------------------------------------
>
>                 Key: HUDI-5432
>                 URL: https://issues.apache.org/jira/browse/HUDI-5432
>             Project: Apache Hudi
>          Issue Type: Bug
>          Components: metadata
>            Reporter: sivabalan narayanan
>            Assignee: Raymond Xu
>            Priority: Blocker
>             Fix For: 0.13.0
>
>
> sample scenario
>  
> lb1_c1, lb2_c2, lb3_c3, lb4_rb_c3, lb5_v4, lb6_c3.
>  
> here we are adding c3 commit, and then rollbacking back c3 (i.e lb3 should be considered invalid).
> after sometime, we add another valid log block with same c3 as commit time. So, we should ensure lb6 is valid here and only lb3 is invalid.
>  
> Especially with repeated attempts of compaction/clustering in DT, very likely this will happen in MDT while trying to update it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)