[
https://issues.apache.org/jira/browse/FLINK-28046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746762#comment-17746762
]
Leonard Xu commented on FLINK-28046:
------------------------------------
[~mxm] There're extra features to be done, but we still lack a lot works listed
in this umbrella ticket to let user migrate to new Source API, current Source
API is to complex for developers even they're experienced flink developers[1],
[~lzljs3620320] and I also have introduced bugs for Apache Paimon Connector
and Flink CDC Connectors due to understanding the new Source API incorrectly :(.
Although I understand the motivation to deprecate the API without waiting any
subtasks, but it still doesn't look like a correct workflow, there're same
concerns[1][2][3] that we should implement these subtasks before we deprecate
this interfaces from umbrella issue or discussion email.
If we must deprecate the API firstly ignore these potential
subtasks(improvements) for the big deprecation API goal of 2.0, I'd like to
propose giving green light to this ticket's workflow and mark the
SourceFunction as deprecated and need someone to say/promise that all subtasks
will be finished in 1.19.
[1]https://issues.apache.org/jira/browse/FLINK-28045?focusedCommentId=17555561&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17555561
[2][https://lists.apache.org/thread/5olmnypjw2nvmsc1m2gmw1btzm9dl3ch]
[3][https://lists.apache.org/thread/d6cwqw9b3105wcpdkwq7rr4s7x4ywqr9]
> 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)
