You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/01/09 19:53:00 UTC

[jira] [Commented] (NIFI-4149) Indicate if EL is evaluated against FFs or not

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

ASF GitHub Bot commented on NIFI-4149:
--------------------------------------

Github user markap14 commented on the issue:

    https://github.com/apache/nifi/pull/2205
  
    @pvillard31 regarding the mock framework: nope, that looks good! I must have just missed it the first time around. Thanks!


> Indicate if EL is evaluated against FFs or not
> ----------------------------------------------
>
>                 Key: NIFI-4149
>                 URL: https://issues.apache.org/jira/browse/NIFI-4149
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Pierre Villard
>            Assignee: Pierre Villard
>
> With the addition of EL in a lot of places to improve SDLC and workflow staging, it becomes important to indicate to users if the expression language enabled on a property will be evaluated against the attributes of incoming flow files or if it will only be evaluated against various variable stores (env variables, variable registry, etc).
> Actually, the expression language (without evaluation against flow files) could be allowed on any property by default, and evaluation against flow files would be what is actually indicated in the UI as we are doing today. Adopting this approach could solve a lot of JIRA/PRs we are seeing to add EL on some specific properties (without evaluation against FFs).
> Having expression language to access external values could make sense on any property for any user. However evaluating the expression language against FFs is clearly a more complex challenge when it comes to session management and such.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)