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