Currently, there is the variable properties file which would require a service restart and also would need to be on all nodes in a cluster.
The last release (1.4.0) added a more user-friendly variable registry in the UI which you can access from the context palette for a given process group, near where the controller services for a PG are located. When editing variables in the UI, it will detect components that reference them and automatically restart them. This variable registry will be tightly integrated with the experience of using the flow registry. Given all of the above, there still isn't anything you can currently do for RPGs though... you will unfortunately have to recreate it in the target environment until they become editable. As far as when the registry will be released, there are no set timelines for apache projects so it will be based when the community believes it is mature enough to be released, and when someone volunteers to be the release manager. That being said, a lot of good work has been done already and it is maturing quickly. Thanks, Bryan On Wed, Nov 8, 2017 at 10:21 AM, wildo <[email protected]> wrote: > Great info Bryan- thanks! > > Regarding my first question, I talked to our admins and we only have one NIC > anyway. So there is no need for me to limit it, and thus I don't have a need > to use EL to discover the NIC. So that's good. > > Regarding the registry stuff, I found this [1] document which looks > FANTASTIC. But I'm not able to find when/if this stuff will be released. My > understanding is that it is not yet released, and therefore I'm assuming > that specifying a custom.properties file via the > nifi.variable.registry.properties is still the preferred method. > Additionally, this will mean that: > 1) Changes to this file require a service restart, correct? > 2) Is it true that this needs to be specified for each node of a clustered > environment? > > Thanks again! > > [1] https://nifi.apache.org/registry.html > > > > -- > Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
