[
https://issues.apache.org/jira/browse/FLINK-33268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17843657#comment-17843657
]
Gabor Somogyi commented on FLINK-33268:
---------------------------------------
> I assume that there can still be a problem, when a newer version client sends
> requests to an old version server with additional fields in RequestBody that
> server does not recognize.
That's correct. This change is not solving the complete set of combinations
just making the client side more flexible. The main use-case what we wanted to
fix is the client usage in the operator code. In short the operator uses a
client and when received a new feature like slot sharing group information
which was added lately then it was blowing up. To overcome this we needed to
copy some things from Flink code which is ugly and in mid-long term must be
removed, for example:
https://github.com/apache/flink-kubernetes-operator/blob/e73363f3486ed9e1df5cc05c9d0baec7c8c3a37f/flink-autoscaler/src/main/java/org/apache/flink/runtime/rest/messages/job/JobDetailsInfo.java#L295
> Flink REST API response parsing throws exception on new fields
> --------------------------------------------------------------
>
> Key: FLINK-33268
> URL: https://issues.apache.org/jira/browse/FLINK-33268
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST
> Affects Versions: 1.19.0
> Reporter: Gabor Somogyi
> Assignee: Gabor Somogyi
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.19.0
>
>
> At the moment Flink is not ignoring unknown fields when parsing REST
> responses. An example for such a class is JobDetailsInfo but this applies to
> all others. It would be good to add this support to increase compatibility.
> The real life use-case is when the Flink k8s operator wants to handle 2 jobs
> with 2 different Flink versions where the newer version has added a new field
> to any REST response. Such case the operator gets an exception when for
> example it tries to poll the job details with the additional field.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
