[
https://issues.apache.org/jira/browse/NIFI-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676319#comment-17676319
]
ASF subversion and git services commented on NIFI-2161:
-------------------------------------------------------
Commit 1d7ee542b121b9ac36412b2a2b3b642d4e0e349c in nifi's branch
refs/heads/main from Chris Sampson
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1d7ee542b1 ]
NIFI-2161 add option to skip attribute output for unmatched JSON path
expressions in EvaluateJsonPath
This closes #6817
Signed-off-by: David Handermann <[email protected]>
> Add option to EvaluateJsonPath to skip adding attributes if the path does not
> match.
> ------------------------------------------------------------------------------------
>
> Key: NIFI-2161
> URL: https://issues.apache.org/jira/browse/NIFI-2161
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Chris Sampson
> Priority: Major
> Fix For: 1.20.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, if one of the paths configured for EvaluateJsonPath does not
> match, the "Null Value Representation" property provides two options - "empty
> string" and "the string 'null'". Unfortunately, if the goal is to check
> whether or not the path is present, neither of these options provides a very
> concise and accurate way of determining whether or not the path actually
> matched the JSON.
> We should add a third option for this property: "Skip Attribute". This value
> would be valid only if the "Destination" property is set to
> "flowfile-attribute". In this case, if the path does not match, the attribute
> will not even be added.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
