[jira] [Closed] (HUDI-6087) Hudi streaming-read is not stopping with savepoint correctly

["Danny Chen (Jira)" <ji...@apache.org>]

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

Danny Chen closed HUDI-6087.
----------------------------
    Resolution: Fixed

Fixed via master branch: 577b2fbb3de6b57d0e1b33b785447991421f83b8

> Hudi streaming-read is not stopping with savepoint correctly
> ------------------------------------------------------------
>
>                 Key: HUDI-6087
>                 URL: https://issues.apache.org/jira/browse/HUDI-6087
>             Project: Apache Hudi
>          Issue Type: Bug
>            Reporter: voon
>            Assignee: voon
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.13.1
>
>
> Flink supports stopping with savepoint as documented here:
> [https://nightlies.apache.org/flink/flink-docs-master/docs/ops/state/savepoints/#stopping-a-job-with-savepoint]
>  
> Stopping with savepoint will invoke these 3 interface functions Flink functions.
>  # cancel()
>  # snapshotState()
>  # close()
>  
> However, the current implementation of stopping with savepoint will cause an *issuedInstant* to be *null* when snapshotState is invoked. This is so as cancel() will set the *issuedInstant* to {*}null{*}, causing the *snapshotState()* to add a *null* value to the *LinkState* list.
>  
> As such, when resuming from a savepoint, there will be:
>  # data loss if the LATEST (by not specifying a value for, i.e. default value) *_read.start.commit_* is used
>  # duplicated data if the EARLIEST *_read.start.commit_* is used
>  
>  
>  



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