You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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.
Search before asking
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?
The text was updated successfully, but these errors were encountered: