[NIFI-2815] Cannot change script engine in InvokeScriptedProcessor

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.1.0
• Assignee: Matt Burgess
• Reporter: Matt Burgess
• Created: 23/Sep/16 15:03
• Updated: 23/Sep/16 17:31
• Resolved: 23/Sep/16 17:31

Description

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.

Issue Links

• is related to: NIFI-2665 InvokeScriptedProcessor intermittently fails validation
• links to: GitHub Pull Request #1055