[
https://issues.apache.org/jira/browse/NIFI-12323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783666#comment-17783666
]
ASF subversion and git services commented on NIFI-12323:
--------------------------------------------------------
Commit 1818d433d61ce19c356b68fa1207d588b4006319 in nifi's branch
refs/heads/support/nifi-1.x from Bryan Bende
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1818d433d6 ]
NIFI-12323 Removed String Length Limits from JSON Flow Configuration
- Configured StreamReadConstraints on the ObjectMapper used by StandardDataFlow
This closes #7985
Signed-off-by: David Handermann <[email protected]>
(cherry picked from commit 940c9276c5ca345739e89ab20db09011a2b6f326)
> StandardDataFlow parsing can hit Jackson StreamReadConstraints issue
> --------------------------------------------------------------------
>
> Key: NIFI-12323
> URL: https://issues.apache.org/jira/browse/NIFI-12323
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.23.2
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Similar to other processors/services that ran into the recent issue from the
> Jackson upgrade that set a default limit on the size of a single string
> value, the same issue can happen in
> {code:java}
> VersionedDataflow parseVersionedDataflow(final byte[] flow) {code}
> Nifi start up will fail because it will be unable to parse the bytes of
> flow.json.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
