NiFi Registry

NiFi Registry is a companion service to Apache NiFi and MiNiFi that stores, versions, and shares flow resources and projects, helping teams deploy data…

  • Development
  • Tools & Utilities
NiFi Registry is a companion service to Apache NiFi and MiNiFi that stores, versions, and shares flow resources and projects, helping teams deploy data workflows consistently across instances and environments.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

20/100 Low

Maintained
0GitHub repository is archived
Popular
41112 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
201 serious finding, 17 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed 2 days ago

GitHub stars
112
Open issues
7
Last commit
2021-07-15
License
Apache-2.0
Activity
stale

Checked 11 days ago - source: GitHub (apache/nifi-registry)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start NiFi after installing it If your install includes NiFi and you used Homebrew, run nifi start from any folder to boot it. Until you do, the NiFi web UI and its services are not running, so you can't reach or configure them. source
  • Protect the file-based user files When using file-based users (people defined in XML files), NiFi reads ./conf/users.xml and ./conf/authorizations.xml, and you should set the Initial Admin Identity. If those files are lost or wrong, you may be locked out or unable to manage accounts. source
  • Repository moved NiFi Registry development has moved into the main Apache NiFi codebase (NIFI-8528). The standalone nifi-registry repository is now a read-only archive. source
  • Repository location The standalone apache/nifi-registry repository is archived and read-only. Development has moved into the main Apache NiFi codebase (NIFI-8528); published Docker images continue under the apache/nifi-registry tag. source

Fetched 42 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What should self-hosters know about NiFi Registry in future NiFi versions?

NiFi 2 supports Git-based Flow Registry clients. NiFi Registry is being removed in NiFi 3.0, so a Git-based registry client can be a migration path.

What should be included when backing up NiFi Registry?

The Registry persistence provider stores version-controlled process groups and is tightly coupled to the registry database. If you use an external GitFlowPersistence provider, that provider may rely on git.

Why can NiFi fail to start version control with a Registry in Docker?

The NiFi and Registry containers must be able to communicate, such as by being on the same Docker network and able to ping each other. Also confirm the Registry URL/path is correct.

Answers sourced from community.cloudera.com, forum.gitea.com, stackoverflow.com

Community

Collected 49 days ago - public community threads