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

Posted to commits@hudi.apache.org by "Qijun Fu (Jira)" <ji...@apache.org> on 2023/04/23 07:52:00 UTC

[jira] [Assigned] (HUDI-6127) Flink Hudi Support Commit on empty batch

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

Qijun Fu reassigned HUDI-6127:
------------------------------

    Assignee: Qijun Fu

> Flink Hudi Support Commit on empty batch 
> -----------------------------------------
>
>                 Key: HUDI-6127
>                 URL: https://issues.apache.org/jira/browse/HUDI-6127
>             Project: Apache Hudi
>          Issue Type: New Feature
>          Components: flink
>            Reporter: Qijun Fu
>            Assignee: Qijun Fu
>            Priority: Major
>
> In flink multi-writer scenario, if one of the writers has no data, it will keep its inflight instant in the timeline. But incremental clean and archive will be blocked by the oldest inflight commit in the timeline.
> So to make clean and archive can move forward  we should upport starting a new instant even when there is no data in the last batch. 



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