[NIFI-476] EvaluateJsonPath fails with NullPointerException on null values

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.1.0, 0.0.2
• Fix Version/s: 0.1.0
• Component/s: Extensions
• Assignee: Aldrin Piri
• Reporter: Brian Ghigiarelli
• Created: 30/Mar/15 17:38
• Updated: 18/Apr/15 04:35
• Resolved: 18/Apr/15 04:35

Description

The EvaluateJsonPath processor fails with a NullPointerException when the input JSON has a null value in the contents of a field it is evaluating.

Caused by: java.lang.NullPointerException
	at org.apache.nifi.processors.standard.AbstractJsonPathProcessor.getResultRepresentation(AbstractJsonPathProcessor.java:84)
	at org.apache.nifi.processors.standard.EvaluateJsonPath.onTrigger(EvaluateJsonPath.java:268)
	at org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)

null is a valid value in the JSON spec

The current spec of EvaluateJsonPath from NIFI-360 indicated that any missing fields should be given an empty string attribute value in the output flow file sent to "match".

null values should either follow this same pattern, or perhaps allow for null values in the output FlowFile attributes to properly indicate the difference between null and an empty String. Either way, EvaluateJsonPath should handle null input values instead of throwing exceptions.

Issue Links

• relates to: NIFI-360 Create Processors to work against JSON data