[ 
https://issues.apache.org/jira/browse/FLINK-25920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631277#comment-17631277
 ] 

Krzysztof Chmielewski edited comment on FLINK-25920 at 11/9/22 8:41 PM:
------------------------------------------------------------------------

[~bdine] and [~qinjunjerry] could you share what kind of Sink are you suing?

Recently we were fixing various issues with Sink architecture for Flink 1.15.
https://issues.apache.org/jira/browse/FLINK-29509
https://issues.apache.org/jira/browse/FLINK-29512
https://issues.apache.org/jira/browse/FLINK-29627

One of the symptoms was this issue for setup with aligned checkpoints. 
You would need to have all 3 of those fixes so you would need to use Flink 
1.15.3 or 1.16.1 (both not yet released).


was (Author: kristoffsc):
[~bdine] and [~qinjunjerry] could you share what kind of Sink are you suing?

Recently we were fixing various issues with Sink architecture for Flink 1.15.
https://issues.apache.org/jira/browse/FLINK-29509
https://issues.apache.org/jira/browse/FLINK-29512
https://issues.apache.org/jira/browse/FLINK-29627

One of the symptoms was this issue for setup with aligned checkpoints. 
You would need to have all 3 of those tickets so you would need to use Flink 
1.15.3 or 1.16.1 (both not yet released).

> Allow receiving updates of CommittableSummary
> ---------------------------------------------
>
>                 Key: FLINK-25920
>                 URL: https://issues.apache.org/jira/browse/FLINK-25920
>             Project: Flink
>          Issue Type: Sub-task
>          Components: API / DataStream, Connectors / Common
>    Affects Versions: 1.15.0, 1.16.0
>            Reporter: Fabian Paul
>            Priority: Major
>
> In the case of unaligned checkpoints, it might happen that the checkpoint 
> barrier overtakes the records and an empty committable summary is emitted 
> that needs to be correct at a later point when the records arrive.



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

Reply via email to