[
https://issues.apache.org/jira/browse/NIFI-12301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-12301:
------------------------------
Status: Patch Available (was: Open)
> When implementing migrateProperties, use of
> PropertyConfiguration.hasProperty() may return wrong result
> -------------------------------------------------------------------------------------------------------
>
> Key: NIFI-12301
> URL: https://issues.apache.org/jira/browse/NIFI-12301
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Critical
> Fix For: 2.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
