[
https://issues.apache.org/jira/browse/FLINK-18450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518770#comment-17518770
]
Piotr Nowojski commented on FLINK-18450:
----------------------------------------
To a very limited extent yes, but for the sake of simplicity you can think of
it that it won't. For this you will need to wait for
https://issues.apache.org/jira/browse/FLINK-27117 (I don't know when it is
going to be ready) which is supposed to address this exact limitation.
The problem is that currently the alignment works by blocking whole operators.
If one operator is responsible for processing both one of the faster splits
(partitions) and the slowest split, then we can not block it as we have to
allow the slowest split to make a progress. However this means the faster split
will be still producing more and more records, causing more and more event
time/watermark (mis)alignment issues. But as it is, this feature might still
help a little bit, as long as you are not unlucky to have the slowest and the
fastest splits processed by the same operator.
> FLIP-182: Support watermark alignment
> -------------------------------------
>
> Key: FLINK-18450
> URL: https://issues.apache.org/jira/browse/FLINK-18450
> Project: Flink
> Issue Type: New Feature
> Components: API / DataStream, Connectors / Common
> Reporter: Jiangjie Qin
> Priority: Major
> Labels: auto-unassigned
> Fix For: 1.15.0
>
>
> With the per-split watermark support, {{SourceReaderBase}} should be able to
> perform watermark alignment so that all the connectors that inherit from it
> would benefit.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
