There is a concept of a variable registry which is described in the Admin Guide here [1], but it is still based on expression language.
For your use case with PutTCP, are you looking to have the hostname paramterized across environments (dev vs prod) or are you looking to connect to a different host per flow file? [1] https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#custom_properties On Mon, Dec 12, 2016 at 10:05 AM, Russell Bateman <[email protected]> wrote: > Without completely understanding your scenario, may I suggest you insert > UpdateAttributes to do this before PutTCP? It supports Expression > Language. > > Hope this helps. > > Russ > > On 12/12/2016 01:04 AM, ddewaele wrote: > > We have a flowfile that contains a number of environment specific values > (ports / hostnames / .....). > > Am I correct in saying that there is no immediate variable registry > somewhere in nifi, and that all of these environment specific items need to > be passed as environment variables or java system properties ? > > I understand that the nifi expression language allows us to retrieve > environment variables / system properties, but a number of processor don't > support the expression language for fields that do contain environment > specific values (like the PutTCP processor hostname property). > > How should we go about updating those ? > > > > -- > View this message in context: > http://apache-nifi-users-list.2361937.n4.nabble.com/Making-FlowFiles-environment-independent-tp409.html > Sent from the Apache NiFi Users List mailing list archive at Nabble.com. > > >
