Behavioral changes denote a marked change in behavior from the previously released version to this version of software.
New Provenance Policy Requirements for NiFi
Apache NiFi 1.7.0 introduces new policies for controlling access to provenance events from a component. When upgrading to Apache NiFi 1.7.0 these new policies will not exist. As a result, users who could previously access provenance events will no longer have access to these provenance events. To ensure continued user access to provenance events, a NiFi administrator must update NiFi policies after upgrade.
Previously, NiFi leveraged the data policies for a component to control access to provenance events but these would also allow a user to download flowfile attributes and content through provenance events and in queues on outgoing connections. Often times granting this much access was too much for the operators of the NiFi instance. However, withholding this access made it difficult for operators to understand the dataflow and track what was happening.
By introducing a new view provenance events policy for controlling access to the event itself these operators can better understand the dataflow and track what is happening while the administrators can still maintain tight control of the flowfile attributes and content. When upgrading to Apache NiFi 1.7.0 these new policies will not exist. As a result, users who could previously access provenance events through the data policies described above will no longer have access to these provenance events.
Expected user action
Before users can access provenance event information, a DataFlow administrator must:
- Create new provenance policies.
- Assign users to the new policies.
NiFi component properties have been renamed
Some NiFi component properties have been renamed.
|Component||Old property||New property|
|GetCouchbaseKey and PutCouchbaseKey||Couchbase Cluster Controller Service||cluster-controller-service|
Expected user action
Old properties become unsupported user-defined properties and the components become invalid. To make the components valid again, migrate the values from the old properties to the new ones, and then remove the old properties.