[
https://issues.apache.org/jira/browse/FLINK-29872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17628776#comment-17628776
]
Chesnay Schepler commented on FLINK-29872:
------------------------------------------
??Why would we design a non backward compatible RestClient if the spec itself
is backward compatible???
a) Remember that the spec came after the current rest client was created.
b) As I said before, the client within Flink can inherently not be fully
compatible with all Flink versions because of the job submission.
That the fields aren't marked as required wasn't actually intentional and is
more a limitation of the current spec.
Even if that were changed though I wouldn't oppose having a second variant that
is less strict, i.e., is similar to the current spec.
Having fields being marked as required simplifies things on both ends; users
know up front what they have to provide and what they get back, and on our side
we don't need to have every handler check 20 preconditions for each request;
instead this is handled generically by the rest framework.
> 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)
