[
https://issues.apache.org/jira/browse/NIFI-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586513#comment-14586513
]
Mark Payne commented on NIFI-688:
---------------------------------
[~mcgilman] When a Processor allows the Expression Language to be used, we
generally can't do much validation because the value will change per FlowFile.
In this case, we could potentially substitute in the value before handing the
value to the Validator.
The thing about this approach that gives me pause, though, is that the
framework guarantees that the values of a Processor's properties will not
change until the Processor is completely stopped. If we went this route, then
we would have to either change that rule (which would break a lot of stuff and
make development more difficult in general) or we would have to prevent the
user from changing a group's variable unless every processor within that group
is completely stopped - and at the root group that can be a pretty big deal.
> 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)
