[
https://issues.apache.org/jira/browse/NIFI-16190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jordan Sammut updated NIFI-16190:
---------------------------------
Description:
When using the *JSLTTransformJSON* processor with *JSON Lines* as the Input
Format, there is currently no way to exclude individual lines when their JSLT
transformation returns {{{}null{}}}.
The *Transform Result Filter* appears to apply to fields within JSON objects
rather than the root-level transformation result. As a result, records
transformed to {{null}} are still written as literal {{null}} lines in the
output.
In the example flow below, we can see that any filtered out records are still
written as null. Ideally, there is a way to filter these out without the use of
another processor:
[^NIFI-16190 - Example Flow.txt]
was:Currently, the *Transform Result Filter* when using the JSLT Transform
using JSON Lines does not perform the filter per line, which would make most
sense. It seems like the filter is performed on the whole Flowfile after all ND
Json Lines are transformed
> JSLTTransformJSON should support filtering out null results in JSON Lines mode
> ------------------------------------------------------------------------------
>
> Key: NIFI-16190
> URL: https://issues.apache.org/jira/browse/NIFI-16190
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Jordan Sammut
> Priority: Major
> Attachments: NIFI-16190 - Example Flow.txt,
> image-2026-10-08-09-10-44-943.png, image-2026-10-09-12-47-02-503.png
>
>
> When using the *JSLTTransformJSON* processor with *JSON Lines* as the Input
> Format, there is currently no way to exclude individual lines when their JSLT
> transformation returns {{{}null{}}}.
> The *Transform Result Filter* appears to apply to fields within JSON objects
> rather than the root-level transformation result. As a result, records
> transformed to {{null}} are still written as literal {{null}} lines in the
> output.
> In the example flow below, we can see that any filtered out records are still
> written as null. Ideally, there is a way to filter these out without the use
> of another processor:
> [^NIFI-16190 - Example Flow.txt]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
