[ 
https://issues.apache.org/jira/browse/FLINK-29872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17628511#comment-17628511
 ] 

Chesnay Schepler commented on FLINK-29872:
------------------------------------------

That's not a compatibility direction that we support in the first place though. 
We only make sure that a client can talk to future versions of Flink, not 
previous versions.

In particular the REST client has problems with compatibility anyway since it 
can submit job graphs that are subject to java serialization (breaking any 
compatibility guarantees anyway).

> 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)

Reply via email to