[jira] [Commented] (NIFI-8730) Invalidate instead of evaluating empty script in scripted components

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-8730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17371958#comment-17371958 ] 

ASF subversion and git services commented on NIFI-8730:
-------------------------------------------------------

Commit 632fbcca7d7e028c4526ab2b643c6b83cfadef99 in nifi's branch refs/heads/main from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=632fbcc ]

NIFI-8730: Invalidate (don't evaluate) empty script in scripting components

Signed-off-by: Pierre Villard <pi...@gmail.com>

This closes #5184.


> Invalidate instead of evaluating empty script in scripted components
> --------------------------------------------------------------------
>
>                 Key: NIFI-8730
>                 URL: https://issues.apache.org/jira/browse/NIFI-8730
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>            Priority: Major
>             Fix For: 1.14.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> As of NIFI-8625, script engines that aren't Invocable are filtered out from the list of available engines to choose for most scripting components (except for ExecuteScript and ScriptedTransformRecord at the time of this writing) as all other scripting components require an Invocable script engine. However this causes ECMAScript to be the default engine, and it throws a NullPointerException when the script body is empty (which it is when the processor is first created).
> Rather than make a different engine be the default (which could be done under a different Jira), it is better to not try to create the ScriptRunner and/or evaluate the script if the body is empty.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)