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

Chesnay Schepler commented on FLINK-28046:
------------------------------------------

I wouldn't put too much emphasize on [1].
The new API is certainly more complex, but after writing/reviewing a few I can 
definitely say that it's possible to do so.
The documentation can absolutely be improved, but blocking the deprecation 
because of that is imo ridiculous.

You ran into issues on the Paimon/CDC side, where are the tickets to fix the 
problems? Flavio ran into issues, where's the ticket for that?
I'd say we should deprecate things precisely to force people to handle these 
problems and not keep clinging onto the SourceFunction interface for dear life.

With the current discussion about having some 1.x it's possibly even less of a 
problem to remove the old source function. Yes, they may mean you can't upgrade 
to 2.0 immediately. Which is fine.

> Annotate SourceFunction as deprecated
> -------------------------------------
>
>                 Key: FLINK-28046
>                 URL: https://issues.apache.org/jira/browse/FLINK-28046
>             Project: Flink
>          Issue Type: Sub-task
>          Components: API / DataStream
>    Affects Versions: 1.15.3
>            Reporter: Alexander Fedulov
>            Assignee: Alexander Fedulov
>            Priority: Major
>              Labels: pull-request-available, stale-assigned
>             Fix For: 1.18.0
>
>




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

Reply via email to