Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/2509
@zenfenan Yeah I think we're on the same page here. Sorry for the different
suggestions earlier but I think we're ultimately getting it right here...
- `All nodes` should be disabled if the component is marked
`PrimaryNodeOnly` regardless of clustered or standalone. However, I think we
should update the tooltip for this field to indicate that it's applicable when
clustered. When not clustered, `All nodes` and `Primary Node` are effectively
the same thing.
- If a processor has been updated to `PrimaryNodeOnly` and its
configuration was previously `All nodes` it should retain that value initially.
However, given the first bullet above, that option will be disabled and would
only allow the user to update it to `Primary node` going forward.
- The field should be always visible regardless of clustered or standalone.
It will allow folks to build flows which may be deployed in a cluster in the
future. It also allows us to remove some of that unnecessarily complex code
when determining the appropriate visibility.
Thanks
---
