[
https://issues.apache.org/jira/browse/FLINK-26759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17510328#comment-17510328
]
Konstantin Knauf commented on FLINK-26759:
------------------------------------------
I am very much with [~martijnvisser] on this. One of the core issues, I think,
has been the slow adoption of the new interfaces in the Flink codebase it self.
This is where we should invest additional resources if we have any. We can not
keep supporting legacy interfaces for ever, so users will have to do the switch
eventually anyway.
For which sources, have you seen issues when upgrading?
> Legacy source support waiting for recordWriter to be available
> --------------------------------------------------------------
>
> Key: FLINK-26759
> URL: https://issues.apache.org/jira/browse/FLINK-26759
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Common, Runtime / Checkpointing
> Affects Versions: 1.13.0, 1.14.0, 1.15.0
> Reporter: fanrui
> Priority: Major
>
> In order for Unaligned Checkpoint not to be blocked, StreamTask#processInput
> will check recordWriter.isAvailable(). If not available, the data will not be
> processed until recordWriter is available.
> The new Source api is compatible with the above logic, but Legacy Source is
> not compatible with the above logic. When using Unaligned Checkpoint, if the
> backpressure of Legacy Source is high, the Checkpoint duration of Legacy
> Source will be very long.
>
> Since legacy sources are often used in production, can we add logic to wait
> for recordWriter to be available for legacy source?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
