[
https://issues.apache.org/jira/browse/FLINK-29872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17628530#comment-17628530
]
Chesnay Schepler commented on FLINK-29872:
------------------------------------------
Then frankly you should use the client from the oldest supported version,
generate a client from the OpenAPI spec for the oldest supported version, or
generate different clients for each Flink version from the OpenAPI spec.
??We simply should not introduce required fields in the rest api.??
Of course we should. Treating every single response field as nullable from now
until the end of time is terrible. I'm not looking forward to having to
null-check every little thing.
> 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)
