[
https://issues.apache.org/jira/browse/NIFI-15712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18065707#comment-18065707
]
David Handermann commented on NIFI-15712:
-----------------------------------------
That could be worth considering. Are you proposing to add JSON Lines support to
{{ValidateJson}}? In light of this change to JoltTransformJSON, I could see
introducing a new {{Input Format}} property to provide support in
{{ValidateJson}}. The initial proposal in that PR, changing the ObjectMapper
configuration, did not seem like the right way forward, but with explicit
configuration, and alternative handling, it could be worth considering.
> Add JSON Lines Support to JoltTransformJSON
> -------------------------------------------
>
> Key: NIFI-15712
> URL: https://issues.apache.org/jira/browse/NIFI-15712
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Fix For: 2.9.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The {{JoltTransformJSON}} Processor should be extended with an new {{JSON
> Source}} strategy supporting [JSON Lines|https://jsonlines.org/], also known
> as Newline Delimited JSON.
> JSON Lines supports multiple JSON elements in a stream, with newline
> character separating each element. This format enables streaming parsing
> where each line is valid JSON.
> The {{JoltTransformRecord}} Processor can be configured for similar
> processing, with appropriate JSON Record Reader and Writer Services, but
> requires a consistent Record Schema for all elements. Adding JSON Lines
> support directly to {{JoltTransformJSON}} enables wider variation of JSON
> input and output elements, without the overhead of Record Schema evaluation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
