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

Matt Gilman commented on NIFI-688:
----------------------------------

[~elcangri2124] Someone else recently made a suggestion that I think would be 
applicable here. The gist of your ticket is to be able to modify multiple 
processors at the same time setting the same property to a new value. The 
suggestion was to allow the user to create process group scoped variables that 
could be substituted into NiFi expression language. Would sometime like this 
address your concerns? 

The idea would be to be able to create these variables when configuring a 
process group. Or in the Flow Settings for system wide variables. This would 
allow for the configuration to be in a single place and then all of the 
processors encapsulated within that group would reference those variables. I 
think this would be a more flexible solution however the only limitation here 
would be that it would only be applicable to properties that support expression 
language. 

[~markap14] Any suggestions on these limitations or is it something we'd have 
to live with?

> Mass processor change
> ---------------------
>
>                 Key: NIFI-688
>                 URL: https://issues.apache.org/jira/browse/NIFI-688
>             Project: Apache NiFi
>          Issue Type: New Feature
>            Reporter: John Lozada
>            Priority: Minor
>
> like discussed in the emails, it would be nice to have a feature where you 
> can select over 100 processors and right click and make a change that is 
> similar in all of them. For example, if I have 100 restpost processors 
> sending to the same server, then I have to change the server, then I should 
> be able to change them all at the same time. I know this can be done with 
> templates or copy and paste but, a easier method would be awesome for those 
> high priority or outages.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to