You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gabor Somogyi (Jira)" <ji...@apache.org> on 2024/01/15 08:57:00 UTC

[jira] [Updated] (FLINK-33268) Flink REST API response parsing throws exception on new fields

     [ https://issues.apache.org/jira/browse/FLINK-33268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabor Somogyi updated FLINK-33268:
----------------------------------
    Fix Version/s: 1.19.0

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