[
https://issues.apache.org/jira/browse/FLINK-29872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17628537#comment-17628537
]
Gyula Fora commented on FLINK-29872:
------------------------------------
You are right we could do many complicated things that might solve a problem
that is introduced by non backward compatible clients. It might not be a
requirement at the moment that the Rest Client is backward compatible but maybe
it should be. We have to understand the costs and the benefits. We can't simply
look at the costs.
I understand that you have a different personal opinion, in that case the
easiest is to discuss in the community because I disagree. If we decide to add
backward compatibilty we might need some null checks or mechanism to set
defaults , but what we get in return can be very valuable for certain users.
> JobDetailsInfo Rest endpoint breaking change in 1.16
> ----------------------------------------------------
>
> Key: FLINK-29872
> URL: https://issues.apache.org/jira/browse/FLINK-29872
> Project: Flink
> Issue Type: Bug
> Components: Runtime / REST
> Affects Versions: 1.16.0
> Reporter: Gyula Fora
> Priority: Major
>
> Flink 1.16 introduces a breaking change to the JobDetailsInfo endpoints by
> adding 3 required fields to:
> [https://github.com/apache/flink/blob/master/flink-runtime/src/main/java/org/apache/flink/runtime/rest/messages/job/metrics/IOMetricsInfo.java]
> accumulatedBackpressured, accumulatedIdle, accumulatedBusy fields should not
> be primitive (which makes them required) but instead nullable.
> This would allow the 1.16 restclient to read the jobdetails of previous
> cluster versions
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
