[jira] [Resolved] (FLINK-35302) Flink REST server throws exception on unknown fields in RequestBody

["Gabor Somogyi (Jira)" <ji...@apache.org>]

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

Gabor Somogyi resolved FLINK-35302.
-----------------------------------
    Resolution: Fixed

36b1d2a on master

> Flink REST server throws exception on unknown fields in RequestBody
> -------------------------------------------------------------------
>
>                 Key: FLINK-35302
>                 URL: https://issues.apache.org/jira/browse/FLINK-35302
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / REST
>    Affects Versions: 1.19.0
>            Reporter: Juntao Hu
>            Assignee: Juntao Hu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.19.1
>
>
> As [FLIP-401|https://cwiki.apache.org/confluence/display/FLINK/FLIP-401%3A+REST+API+JSON+response+deserialization+unknown+field+tolerance] and FLINK-33268 mentioned, when an old version REST client receives response from a new version REST server, with strict JSON mapper, the client will throw exceptions on newly added fields, which is not convenient for situations where a centralized client deals with REST servers of different versions (e.g. k8s operator).
> But this incompatibility can also happens at server side, when a new version REST client sends requests to an old version REST server with additional fields. Making server flexible with unknown fields can save clients from backward compatibility code.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)