You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Uladzimir Palkhouski (JIRA)" <ji...@apache.org> on 2017/04/24 19:26:04 UTC

[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&focusedCommentId=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)