Behavioral changes

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

Summary: Incompatible changes in schema validation in Avro 1.11

In Avro, when a schema is present, all required fields are defined by the schema. If a field is missing in the input data, a java.lang.NullPointerException is raised. Conversely, when there is an extra field in the input data not defined by the schema, the field is ignored, and the RecordWriter excludes it from serialization.

Avro 1.11 has introduced a more strict schema validation, which leads to changes in default value handling. This change might impact existing flows. In previous Avro versions, you cloud set the default value of a complex type as null' to indicate that it is not required.

However, with Avro 1.11 introduced, if a field is missing, parsing fails with org.apache.avro.AvroTypeException. To address this, it is now necessary to specify null as a valid type in the schema before you can assign it as a default value.

Summary: Change in default encryption algorithm for NiFi sensitive properties

In CFM 2.1.5, the default algorithm used for encrypting NiFi sensitive properties in the NiFi flow configuration file has has been updated to enhance encryption security.

If you are using Cloudera Manager to upgrade to CFM 2.1.5, this algorithm change is managed automatically.

If you are manually migrating the NiFi files to a new CFM 2.1.5 cluster, you are required to update the encryption algorithm. For instructions, see Updating encryption algorithm for sensitive properties.