[jira] [Commented] (NIFI-8933) Jersey ObjectMapper should ignore unknown fields

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on NIFI-8933:
-------------------------------------------------------

Commit 74c0a91b6c9c25f348518c8700f998b422a341f9 in nifi's branch refs/heads/main from Bryan Bende
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=74c0a91 ]

NIFI-8933 Configure Jersey's ObjectMapper to ingnore unknown fields

Signed-off-by: Pierre Villard <pi...@gmail.com>

This closes #5236.


> Jersey ObjectMapper should ignore unknown fields
> ------------------------------------------------
>
>                 Key: NIFI-8933
>                 URL: https://issues.apache.org/jira/browse/NIFI-8933
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 1.14.0
>            Reporter: Bryan Bende
>            Assignee: Bryan Bende
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The ObjectMapper used by Jersey is configured in ObjectMapperResolver and does not specify any configuration related to unknown fields, so the default is to fail.
> This can be problematic when trying to import a flow definition that may have been produced with a newer NiFi version than the current one, and therefore has new fields.
> This works when we import from registry because the registry client uses a different ObjectMapper, and the same for when using the UI to create a new process group from a file, but it fails using the process group replacement REST API.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)