nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre Villard (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (NIFI-2815) Cannot change script engine in InvokeScriptedProcessor
Date Fri, 23 Sep 2016 17:32:20 GMT

     [ https://issues.apache.org/jira/browse/NIFI-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pierre Villard updated NIFI-2815:
---------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> 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)

Mime
View raw message