[NIFI-5230] InvokeScriptedProcessor can issue a NullPointerException in customValidate

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.6.0
• Fix Version/s: 1.7.0
• Assignee: Matt Burgess
• Reporter: Matt Burgess
• Created: 23/May/18 13:48
• Updated: 23/May/18 15:11
• Resolved: 23/May/18 14:08

Description

NIFI-4968 improved the behavior of InvokeScriptedProcessor when the script has an error during parsing/interpretation/compilation, and an improvement was made to not output the same validation errors over and over again until manual action was taken. As part of that improvement though, a bug was introduced where a NullPointerException can occur.

Proposed fix is not to set the validation results to null on "clear", but rather to an empty Set (which the code is expecting)

Issue Links

• links to: GitHub Pull Request #2734