[
https://issues.apache.org/jira/browse/NIFI-13542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17866470#comment-17866470
]
ASF subversion and git services commented on NIFI-13542:
--------------------------------------------------------
Commit b9b5c03b2ecb44291c53362841f933dbcbf66297 in nifi's branch
refs/heads/support/nifi-1.x from Mark Bathori
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b9b5c03b2e ]
NIFI-13542 Added missing Max String Length property for JSON Readers (#9084)
Signed-off-by: David Handermann <[email protected]>
> Fix missing max string length parameter usage in multiple JSON Readers and
> Schema Access Strategy
> -------------------------------------------------------------------------------------------------
>
> Key: NIFI-13542
> URL: https://issues.apache.org/jira/browse/NIFI-13542
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Mark Bathori
> Assignee: Mark Bathori
> Priority: Major
> Fix For: 2.0.0-M5
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Jackson lib 2.15.0 introduced an upper limit for string length so there were
> a couple of tickets (NIFI-12117, NIFI-12127, NIFI-12153) that addressed this
> issue in some components by introducing a new property to make the maximum
> sting length configurable, but there are still some occurrences where this
> parameter usage is missing.
>
> The following components are still using the default string length value:
> * Infer Schema Access Strategy in JSON Readers
> * JsonPathRowRecordReader
> * YamlTreeReader
> * JsonRecordSource
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
