[
https://issues.apache.org/jira/browse/FLINK-36476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890062#comment-17890062
]
david radley commented on FLINK-36476:
--------------------------------------
[~xuyangzhong] I think getting wider points of view from the community will
help.
If we decide to remove I suggest we mitigate the impact by listing the removed
Python functions in the release notes.
If we decide to keep the Python functions , we could mark them as deprecated,
and change the implementation so that is does not use the deprecated JAVA API,
so we can remove it.
I do not have strong views which way we should go, but, on balance, I would
agree with you, to remove and document the Python APIs in this category, so we
have a lower attack surface and push users away from driving legacy code and
towards the better up-to-date code.
> Remove all deprecated methods under public APIs in table modules and adapt
> the related tests to make them pass
> --------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-36476
> URL: https://issues.apache.org/jira/browse/FLINK-36476
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Reporter: xuyang
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.0.0
>
>
> All methods needed to be removed are:
> [https://docs.google.com/document/d/1bVrmcB9UFOd1-sT7xDRTMb5rmO0vK0eDlLRUYYL9gd4/edit?usp=sharing]
>
> Note:
> # Please make sure to delete and adapt the code(including test) of module
> table, python, doc, etc. as well.
> # Please raise a PR in the corresponding subtask, and try not to link PRs on
> this umbrella jira.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
