[NIFI-2161] Add option to EvaluateJsonPath to skip adding attributes if the path does not match.

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.20.0
• Component/s: Extensions
• Assignee: Chris Sampson
• Reporter: Mark Payne
• Created: 01/Jul/16 13:39
• Updated: 17/Jan/23 20:03
• Resolved: 12/Jan/23 20:06

Description

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.

Issue Links

• links to: GitHub Pull Request #6817