Cloudera Docs

Behavioral changes

Learn about behavioral changes in Cloudera Flow Management (CFM) 2.1.6.

Updated permissions required for process group version control
Starting or changing version control for a process group now requires users to have "view" permissions on the "Access the controller" global policy. Without this permission, the UI will display a continuous spinner in the toolbar, and the Flow Version UI will not appear.
Update permissions as needed to avoid UI issues when managing process group version control.
Neo4JCypher3ClientService removal
The Neo4JCypher3ClientService Controller Service has been removed and replaced with the Neo4JCypherClientService controller service, which uses a more recent version of the underlying library.
JndiJmsConnectionFactoryProvider security restrictions
As part of NIFI-11614 new security restrictions have been implemented for the JndiJmsConnectionFactoryProvider controller service.
By default, the JNDI Provider URL property now only allows the following URL schemes:
  • file
  • jgroups
  • ssl
  • t3
  • t3s
  • tcp
  • udp
  • vm
If an additional URL scheme is required for a specific JMS solution, a NiFi administrator has to configure the following Java system property in the application bootstrap.conf file to override the default list: java.arg.jndiJmsUrlSchemesAllowed=-Dorg.apache.nifi.jms.cf.jndi.provider.url.schemes.allowed=ssl tcp
ScriptedTransformRecord processor requires proper schema name attribute for record writer
NIFI-11523 introduced a fix that ensures the ScriptedTransformRecord processor uses the correct schema defined for the record writer.
Previous behavior:
If the schema name attribute was set in the writer but not in the flow, NiFi ignored it and defaulted to the reader schema.
Updated behavior:
The processor now requires the schema name attribute in the flow to correctly apply the intended schema. If the schema name is missing, the processor may fail after upgrading.
Typical error message:
org.apache.nifi.schema.access.SchemaNotFoundexception: ${schema.name} did not provide appropriate Schema Name

To prevent failures, ensure that the schema name attribute is properly configured in the flow or matches the schema defined for the record reader for identical behavior.