[
https://issues.apache.org/jira/browse/FLINK-28046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17745250#comment-17745250
]
Alexander Fedulov commented on FLINK-28046:
-------------------------------------------
[~leonard] [~xtsong]
Just to clarify, is marking "Deprecated" equal to "can be completely removed
right away" for you? If so, is it defined as such somewhere in the project
bylaws? I'd like to understand what speaks against using it for communicating
that the interface is due to be removed so that users are aware that they need
to start using the future-proof alternative. Ultimately, the longer the API
remains Public, the more pain it will induce when it is finally dropped. What
is the benefit in waiting for all the items in FLINK-28045 to be complete both
for us and for the users?
> 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)
