[
https://issues.apache.org/jira/browse/FLINK-31588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709783#comment-17709783
]
Piotr Nowojski commented on FLINK-31588:
----------------------------------------
Sorry for late response, I've just found an old tab with WIP comment that I
wanted to write, but somehow didn't send as something must have interrupted me
:(
Thanks for reporting the issue. I see the problem. I think ideally we should
try to keep the semantic of that flag in sync with what {{StreamTask}} was
actually doing. If checkpoint was unaligned, as it arrived unaligned, it should
be reported as such, even if that particular subtask didn't persist any data.
Can we still achieve that?
> The unaligned checkpoint type is wrong at subtask level
> -------------------------------------------------------
>
> Key: FLINK-31588
> URL: https://issues.apache.org/jira/browse/FLINK-31588
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing
> Affects Versions: 1.16.0, 1.17.0
> Reporter: Rui Fan
> Assignee: Rui Fan
> Priority: Major
> Attachments: image-2023-03-23-18-45-01-535.png
>
>
> FLINK-20488 supported show checkpoint type for each subtask, and it based on
> received `CheckpointOptions` and it's right.
> However, FLINK-27251 supported timeout aligned to unaligned checkpoint
> barrier in the output buffers. It means the received `CheckpointOptions` can
> be converted from aligned checkpoint to unaligned checkpoint.
> So, the unaligned checkpoint type may be wrong at subtask level. For example,
> as shown in the figure below, Unaligned checkpoint type is false, but it is
> actually Unaligned checkpoint (persisted data > 0).
>
> !image-2023-03-23-18-45-01-535.png|width=1879,height=797!
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
