A dataflow estate that can't stop to upgrade
NiFi 1.x is past community end of life, and NiFi 2 is a breaking change -- not a version bump a running dataflow estate absorbs on a security timeline.
Challenge
NiFi flows accumulate: hundreds of processors, custom controller services, and dataflows built by people who have since moved on. A NiFi 2 migration means auditing all of it, while the flows keep running production data.
Environment
Apache NiFi 1.x carrying production dataflows, with a processor and controller-service inventory built up over years.
Approach
OSSeva patches the NiFi 1.x line so the estate is covered, then scopes the NiFi 2 move against the actual processor inventory rather than a generic upgrade guide.
What this delivers
CVE coverage on the running dataflow estate, and a NiFi 2 migration planned against what is actually deployed.