Behavioral changes

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

Summary:

The Neo4JCypher3ClientService Controller Service has been completely removed in favor of the Neo4JCypherClientService controller service, which uses a more recent version of the underlying library.

Summary:

As part of NIFI-11614 and to ensure better security, some restrictions around the JndiJmsConnectionFactoryProvider controller service have been implemented.

The default validation for the JNDI Provider URL property only allows the following URL schemes:

file
jgroups
ssl
t3
t3s
tcp
udp
vm

If an additional URL scheme is required to interact with a specific JMS solution, a NiFi admin 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

Summary: 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. Previously, if the schema name attribute was set in the writer but not in the flow, it was ignored, defaulting to the reader schema. This behavior has been corrected, which may cause the processor to fail after upgrading if the schema name attribute is not set in the flow.

The failure is typically logged as:

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 match it to the schema defined for the record reader for identical behavior.