You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Peter Wicks (JIRA)" <ji...@apache.org> on 2018/06/26 16:42:00 UTC

[jira] [Commented] (NIFI-764) Add support for global variables

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

Peter Wicks commented on NIFI-764:
----------------------------------

I think this can be cancelled/closed as covered by the updates in past versions to Variables.

> Add support for global variables
> --------------------------------
>
>                 Key: NIFI-764
>                 URL: https://issues.apache.org/jira/browse/NIFI-764
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework, Core UI
>            Reporter: Matt Gilman
>            Priority: Minor
>
> Add support for global variables (possibly scoped at a group level). These could be used within NiFi expression language providing support for more portable templates and bulk configuration changes.
> The general idea is that the user will be able to define a variable name and value and then use it within expression language. At this point they would be able to export a template with components referencing the variables. When imported into another NiFi instance with the same variables defined, it provides an easy way to move a flow between different environment and update it's configuration in a single action (like when values for development and production differ per instance).
> Another benefit of an approach like this, it that it could allow for bunk edits. If multiple components reference the same variable (e.g. xxxx.post.uri), it allows the user to make that change in a single location rather than having to identify each instance of that value. Will obviously need to consider the mechanics when modifying a variable as it will require all referencing components to be stopped.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)