how to keep Environmental property file in cache , which will be used across the processor.

[#1]

Hi Team,

I have requirement like need to read the environment property file and keep in memory, also need to auto refresh is any update done in property file. Example Env.properties

parent_path = /sourcesystem/country/

Auth_key = 234234fsdaf234

password =**************

IN = india

i need to use the above property in my processor across the flow. Example in ListFile processor i want to use ${parent_path} , this should replace "/sourcesystem/country/ " value.

[#2 · Accepted solution]

There are 2 ways to do it:

1) Custom properties file

• put name=value pairs in custom property file: parent_path=/sourcesystem/country/
• put custom property file in a location you choose on the nifi cluster
• open the existing nifi.properties file
• for property nifi.variable.registry.properties, set it to the path to your custom property file (or a csv of a list of custom property files)
• in your processor, use ${parent_path} as you indicate

2) OS environment variable (best for sensitive values not to be exposed in a file)

• set the OS environment variable: export Auth_key=234234fsdaf234
• reference ${Auth_key} in your processor

The following links show more details

• https://community.hortonworks.com/articles/60868/enterprise-nifi-implementing-reusable-components-a....
• https://community.hortonworks.com/articles/57304/supporting-custom-properties-for-expression-langua....

[#3]

I tried with 1) Custom properties file. This is working. Thank you Greg Keys

[#4]

Thanks @Greg Keys for your quick response. Custom Properties file is working absolutely fine

[#5]

Glad it helped 🙂 (If you want to get more reuse from nifi, see first link in answer for reusing templates during development).