You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Burgess (JIRA)" <ji...@apache.org> on 2018/05/23 13:54:00 UTC
[jira] [Updated] (NIFI-5230) InvokeScriptedProcessor can issue a
NullPointerException in customValidate
[ https://issues.apache.org/jira/browse/NIFI-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Burgess updated NIFI-5230:
-------------------------------
Status: Patch Available (was: In Progress)
> InvokeScriptedProcessor can issue a NullPointerException in customValidate
> --------------------------------------------------------------------------
>
> Key: NIFI-5230
> URL: https://issues.apache.org/jira/browse/NIFI-5230
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.6.0
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
>
> 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)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)