[NIFI-12301] When implementing migrateProperties, use of PropertyConfiguration.hasProperty() may return wrong result

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 2.0.0-M1
• Component/s: Core Framework
• Assignee: Mark Payne
• Reporter: Mark Payne
• Created: 31/Oct/23 21:21
• Updated: 09/Nov/23 23:35
• Resolved: 01/Nov/23 15:42

Description

When making use of PropertyConfiguration.hasProperty(String) or PropertyConfiguration.hasProperty(PropertyDescriptor), the method always returns true if the property is defined in the component evaluating it - even when the property did not exist in the previous build.

Before calling migrateProperties we apply the configuration to the Processor/Controller Service/Reporting Task. We then create the PropertyConfiguration based on that. So, if the property descriptor is defined in the new version, hasProperty will return true, even if it was not in the properties of the previous version of the component.

Issue Links

• causes: NIFI-12339 Sensitive Dynamic Properties not properly decrypted, resulting in wrong property value and ever-growing flow.json.gz
• links to: GitHub Pull Request #7964