Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Avoid deprecated APIs removed in Flink 2.0 Preview #4442

Open
2 tasks done
yunfengzhou-hub opened this issue Nov 4, 2024 · 2 comments · May be fixed by #4567
Open
2 tasks done

[Feature] Avoid deprecated APIs removed in Flink 2.0 Preview #4442

yunfengzhou-hub opened this issue Nov 4, 2024 · 2 comments · May be fixed by #4567
Labels
enhancement New feature or request

Comments

@yunfengzhou-hub
Copy link
Contributor

yunfengzhou-hub commented Nov 4, 2024

Search before asking

  • I searched in the issues and found nothing similar.

Motivation

Flink 2.0 Preview has been released, and Paimon needs to make itself compatible with 2.0 Preview now, to be better prepared for the Flink 2.0 in future.

Solution

A bunch of public APIs that had been marked as @Deprecated are now removed in Flink 2.0 Preview. Paimon needs to replace usages of these deprecated APIs to the latest alternatives.

Anything else?

Flink 2.0 still have more work to do with its internal implementation, and only dealt with its public APIs in 2.0 Preview. So if Paimon has been using Flink's public methods that are not marks as @Public or @PublicEvolving, the usages might still be compatible with 2.0 Preview for now, but should also be updated to alternatives as early as possible.

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@yunfengzhou-hub yunfengzhou-hub added the enhancement New feature or request label Nov 4, 2024
@yunfengzhou-hub
Copy link
Contributor Author

Apart from deprecated public APIs, Paimon has also been using internal public methods or private methods through reflection. These usages bring risks to Paimon's compatibility to Flink as these internal implementations might be modified at any time. They should also be replaced as part of this issue.

@wwj6591812
Copy link
Contributor

Good work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants