[
https://issues.apache.org/jira/browse/FLINK-33268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Somogyi updated FLINK-33268:
----------------------------------
Description:
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.
was:
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 tries to
poll the job details with the additional field.
> Flink REST API response parsing should support backward compatible changes
> like 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
> Priority: Major
>
> 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)
