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

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

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

NIFI-7260: Fix error handling and re-evaluate Module Directory property on 
changed for scripted controller services

This closes #4147

Signed-off-by: Mike Thomsen <[email protected]>


> Scripted controller services do not handle Module Directory changes or script 
> errors properly
> ---------------------------------------------------------------------------------------------
>
>                 Key: NIFI-7260
>                 URL: https://issues.apache.org/jira/browse/NIFI-7260
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>            Priority: Major
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Currently for all scripted controller services (ScriptedReader, e.g.) the 
> scripting engine (with additional classpath modules defined by the Module 
> Directory property) is only recreated when the Script Engine property has 
> changed. It should be recreated when the Module Directory property has 
> changed as well.
> In addition, the controller service can be enabled even with an error in the 
> script. The controller service reports internally that it is invalid, but 
> becomes enabled anyway, hiding the invalid status from the user. They may 
> also suffer from the issue in NIFI-4968 with logging while the script is 
> invalid. Instead an exception should be thrown, which prevents the CS from 
> being enabled, then the fix from NIFI-4968 should be applied so that 
> excessive logging does not occur while the CS is invalid.



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

Reply via email to