NIFI Lookup processor service - NOT by GUID

[John Gunvaldson <jg...@cox.net>]

All, 

General question on exploring the option for building a lookup service for NIFI.

Problem 1 --> When deploying a flow to another environment - GUID is not maintained, often the flow will obtain another GUID upon deployment into another environment.

Problem 2 --> If you have automated a service in another environment (lets call it Airflow for an example) - and job is to use the NipyApi, find the processor, and schedule the processor or alter a property or change a metric or something

Using NipyApi and using GUID - no problem, can pretty quickly identify the processor and do your work

However, now you have moved that flow to another environment - and the processor no longer has the same GUID, in fact changes after every deployment, constant change

I am exploring some ideas on how to solve this.

1. Build a cache of everything in NIFI - and if you traverse the cache along the expected Processor Group path — Root Canvas — Process Group A — Process Group B - then look for your processor named this here - and return something identifiable - probably current GUID?

2. Other ideas - what kind of “Recursive Name Lookup Services” have others built that work in this scenario?


Thanks in Advance
~ John