Thank you Bryan. On Thu, Apr 19, 2018 at 6:49 PM, Bryan Bende <[email protected]> wrote:
> You can also set system properties in bootstrap.conf, this was the > primary way of setting up variables before either of the variable > registries existed. > > java.arg.123=-Dmyvar=myvalue > > On Thu, Apr 19, 2018 at 8:41 AM, Matt Burgess <[email protected]> > wrote: > > If you are using a version of NiFi that has ExecuteScript, you could > > write a script that reads in the properties from that file and create > > flow file attributes from them, then for downstream processors that > > accept incoming flow files and evaluate Expression Language against > > them, you'll be able to refer to those "properties" in the expression. > > > > Regards, > > Matt > > > > On Thu, Apr 19, 2018 at 4:54 AM, saloni udani <[email protected]> > wrote: > >> Hi > >> > >> There are two ways to use and manage custom properties in NiFi: > >> -In the NiFi UI via the Variables window > >> -Referencing custom properties via 'nifi.properties' > >> > >> But I am using older version of NiFi which doesn't have variable > registry > >> support.So is it possible to refer to the properties from > nifi.properties > >> directly (without setting nifi.variable.registry.properties) in the > >> processor property which supports expression language? > >> > >> E.g If I want to use 'nifi.cluster.node.address' from nifi.properties > as a > >> value to a processor’s property ${nifi.cluster.node.address} > >> > >> > >> Thank you >
