[jira] [Commented] (NIFI-2152) ExecuteScript throws Exception when Using NiFi Expression in ScriptPath
[ https://issues.apache.org/jira/browse/NIFI-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545095#comment-16545095 ] Mike Thomsen commented on NIFI-2152: [~mattyb149] further up in Jira, I saw someone mention that they're working on a PR to move to Compilable. That's going to greatly complicate this ticket, but will be well worth it if it's done right. > ExecuteScript throws Exception when Using NiFi Expression in ScriptPath > --- > > Key: NIFI-2152 > URL: https://issues.apache.org/jira/browse/NIFI-2152 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 0.6.1 >Reporter: Christopher Reeves >Priority: Major > > The ExecuteScript Processor throws in an Exception in the "setup" method when > using a NiFi Expression for the script Path argument. Ideally, the script > would be read in the onTrigger Method of the processor to allow for setting > the desired script on a dynamic basis. > A RouteAttributeProcessor can be used as a workaround to point to many > ExecuteScript processor. However, depending on the number of scripts > required, this can lead to a cluttered flow configuration which can be > difficult to follow and much more difficult to maintain. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-2152) ExecuteScript throws Exception when Using NiFi Expression in ScriptPath
[ https://issues.apache.org/jira/browse/NIFI-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982026#comment-15982026 ] Matt Burgess commented on NIFI-2152: When a property supports Expression Language, it is not guaranteed to evaluate the expression against an incoming flow file. The Script File property does indeed support Expression Language, but it does not evaluate the expression against an incoming flow file, so only references to system/environment/variable registry variables are evaluated. This is done for performance reasons, so as not to read in a file and evaluate a script upon each call to onTrigger(). This could be clarified in the documentation for sure. I would recommend keeping this Jira case for its original purpose (to support flow file attributes in Expression Language constructs in the Script File property), and writing up a new one for documentation clarification. > ExecuteScript throws Exception when Using NiFi Expression in ScriptPath > --- > > Key: NIFI-2152 > URL: https://issues.apache.org/jira/browse/NIFI-2152 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 0.6.1 >Reporter: Christopher Reeves > > The ExecuteScript Processor throws in an Exception in the "setup" method when > using a NiFi Expression for the script Path argument. Ideally, the script > would be read in the onTrigger Method of the processor to allow for setting > the desired script on a dynamic basis. > A RouteAttributeProcessor can be used as a workaround to point to many > ExecuteScript processor. However, depending on the number of scripts > required, this can lead to a cluttered flow configuration which can be > difficult to follow and much more difficult to maintain. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-2152) ExecuteScript throws Exception when Using NiFi Expression in ScriptPath
[ https://issues.apache.org/jira/browse/NIFI-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15981738#comment-15981738 ] Uladzimir Palkhouski commented on NIFI-2152: Issue is still present in 1.1.2 At the moment there is no way to applly dynamic JSON transformation because: - JoltTransformJson does not support dynamic expressions - ExecuteScript does support dynamic expressions for scripf file attribute, however fails to load the script when the path is defined through dynamic expression Seems to be limitation of the platform. Knowing that there is fix in 1.2.0 for support of expression language in JoltTransformJson the proposal is to remove dynamic expressions support from official documentation for Scrip File attribute of ExecuteScript, unless it is going to be fixed. > ExecuteScript throws Exception when Using NiFi Expression in ScriptPath > --- > > Key: NIFI-2152 > URL: https://issues.apache.org/jira/browse/NIFI-2152 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 0.6.1 >Reporter: Christopher Reeves > > The ExecuteScript Processor throws in an Exception in the "setup" method when > using a NiFi Expression for the script Path argument. Ideally, the script > would be read in the onTrigger Method of the processor to allow for setting > the desired script on a dynamic basis. > A RouteAttributeProcessor can be used as a workaround to point to many > ExecuteScript processor. However, depending on the number of scripts > required, this can lead to a cluttered flow configuration which can be > difficult to follow and much more difficult to maintain. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-2152) ExecuteScript throws Exception when Using NiFi Expression in ScriptPath
[ https://issues.apache.org/jira/browse/NIFI-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576403#comment-15576403 ] Matt Burgess commented on NIFI-2152: Removing easyfix label, supporting Expression Language (where the attribute values may come from flow files) would require some refactor. Also there are performance impacts to be considered (especially in regard to NIFI-1822). > ExecuteScript throws Exception when Using NiFi Expression in ScriptPath > --- > > Key: NIFI-2152 > URL: https://issues.apache.org/jira/browse/NIFI-2152 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 0.6.1 >Reporter: Christopher Reeves > > The ExecuteScript Processor throws in an Exception in the "setup" method when > using a NiFi Expression for the script Path argument. Ideally, the script > would be read in the onTrigger Method of the processor to allow for setting > the desired script on a dynamic basis. > A RouteAttributeProcessor can be used as a workaround to point to many > ExecuteScript processor. However, depending on the number of scripts > required, this can lead to a cluttered flow configuration which can be > difficult to follow and much more difficult to maintain. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
