Learn about the change in behavior in Cloudera Flow Management (CFM) 2.1.4.
CFM 2.1.4 NiFi started using a
flow.json.gzinstead of the
flow.xml.gzfile used in all previous versions. On startup, NiFi converts the existing
flow.json.gzfile. If a
flow.json.gzalready exists, NiFi ignores the
flow.xml.gzon startup. Changes made on the canvas will currently be written to both the new
flow.json.gzversion as well as the
flow.xml.gzfile; however, only the
flow.json.gzis loaded on NiFi startup.
Following some security related changes and dependency upgrades, the list of supported databases for the NiFi Registry component has changed. Make sure you are using a supported version before upgrading to CFM 2.1.4. For more information, see the Support matrix.
The Kafka processors previously distributed for interacting with Kafka 0.x clusters have been removed. It means that these processors are no longer provided nor supported by Cloudera and it is recommended to switch to the processors making use of Kafka 2.x versions.
Elasticsearch processors that were leveraging the Elasticsearch 2.0 library and the deprecated Transport Client have been removed. It means that the below processors are no longer provided and supported by Cloudera. It is recommended to switch to the processors interacting with Elasticsearch over HTTP.