What's New in Flow Management

Learn about the new Flow Management features in Cloudera DataFlow for Data Hub 7.2.9.

The Flow Management clusters in CDP Public Cloud introduces the following features:

Restricted-component policy is more granular
Fine-tune access by a restricted component to the localhost filesystem data by specifying the restricted component and type of permission in the policy that you assign to the user or user group. This also makes a distinction between processors that can access the local filesystem where NiFi is running and the processors that can access a distributed file system like the Hadoop related processors.

For more information, see NiFi Restricted Components.

NiFi-Ozone integration
If Ozone is installed in your CDP cluster, you can use the HDFS processors in NiFi to interact with the Ozone storage layer.
NiFi node status history and status repository
You can now access a Node Status History view from the hamburger menu. This provides useful monitoring data about the NiFi nodes in the cluster over time. Just like Status History data at the component level, Node History data is stored in memory by default and removed after a NiFi restart.
It is now possible to persist both Node and Status history data by setting the nifi.components.status.repository.implementation property in the nifi.properties file.

For more information, see the Status History Repository topic in the Apache NiFi Administration Guide.

NiFi Registry - Database flow persistence provider

The external database provisioned with the Data Hub cluster which is used as the external database for the NiFi Registry instance, will now also be used as the flow persistence provider. The versioned flow definitions will no longer be stored locally on the file system. This provides a greater resilience for the data versioned in NiFi Registry.