[
https://issues.apache.org/jira/browse/NIFI-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15517055#comment-15517055
]
ASF subversion and git services commented on NIFI-2815:
-------------------------------------------------------
Commit 66fe004058ca9f4d9933f49865572c4dac3cbfdb in nifi's branch
refs/heads/master from [~mattyb149]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=66fe004 ]
NIFI-2815: Fixed InvokeScriptedProcessor to allow changes to script engine type
This closes #1055.
> Cannot change script engine in InvokeScriptedProcessor
> ------------------------------------------------------
>
> Key: NIFI-2815
> URL: https://issues.apache.org/jira/browse/NIFI-2815
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Fix For: 1.1.0
>
>
> Due to a regression introduced in NIFI-2665, the script engine for an
> InvokeScriptedProcessor is instantiated only once. For instances already in
> the flow, the Script Engine property setting will be honored, but it cannot
> be changed. For new InvokeScriptedProcessor instances, the script engine will
> be set to ECMAScript and also cannot be changed.
> Seems that before NIFI-2665, script engine setup was happening too often, now
> it is not happening enough. The script engine should be reset when the
> property has been modified.
> A workaround is to change the processor to the way you want it, then save it
> as a template, then delete the original and re-load it from the template.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
