[
https://issues.apache.org/jira/browse/NIFI-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586526#comment-14586526
]
Mark Payne commented on NIFI-688:
---------------------------------
[~mcgilman] Well you've got a point there - i guess someone could change a
system or environment variable at runtime. But the only way to reference those
now would be via the Expression Language. So there's generally no validation
done there anyway (StandardValidators.NON_EMPTY_VALIDATOR).
My thought was that if the user entered a value like ${my.group.var} then we
could substitute that in and do proper validation... not sure if it's a good
idea because it may be too confusing for users - sometimes you evaluate the
expression language (when only referencing a group variable), sometimes you
don't (when referencing any other variable).
I think we should avoid treating this as a special use case and just live with
the limitation that they can only be referenced when a Processor allows the
Expression Language to be used.
> 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)