Replies: 2 comments 2 replies
-
I agree with that. From a technical perspective, the flink-optimizer should be able to achieve engine versions independence. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I agree with the idea, but currently, using a fixed set of profiles to expose the Flink optimizer's dependency on Flink versions seems to limit the use of more Flink versions. Perhaps we should directly expose the ability to set the Flink version used through parameters, which would be more scalable. For example, like this:
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Amoro Optimizer Now Just Supports Flink 1.14 to Flink 1.16, Maybe We can upgrade it to support Flink 1.15/1.16/1.17/1.18, and remove Flink 1.14 support.
Beta Was this translation helpful? Give feedback.
All reactions