[jira] [Commented] (NIFI-2815) Cannot change script engine in InvokeScriptedProcessor

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)

[jira] [Commented] (NIFI-2815) Cannot change script engine in InvokeScriptedProcessor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2815:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/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)

[jira] [Commented] (NIFI-2815) Cannot change script engine in InvokeScriptedProcessor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2815:
--

Github user pvillard31 commented on the issue:

https://github.com/apache/nifi/pull/1055
  
+1 merging into master


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

[jira] [Commented] (NIFI-2815) Cannot change script engine in InvokeScriptedProcessor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2815:
--

Github user brosander commented on the issue:

https://github.com/apache/nifi/pull/1055
  
+1


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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2815) Cannot change script engine in InvokeScriptedProcessor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2815:
--

GitHub user mattyb149 opened a pull request:

https://github.com/apache/nifi/pull/1055

NIFI-2815: Fixed InvokeScriptedProcessor to allow changes to script engine 
type



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mattyb149/nifi NIFI-2815

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1055.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1055


commit 6803255505fb845cd999b9704f06db55a54083d8
Author: Matt Burgess 
Date:   2016-09-23T15:04:51Z

NIFI-2815: Fixed InvokeScriptedProcessor to allow changes to script engine 
type




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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)