[
https://issues.apache.org/jira/browse/NIFI-14985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-14985:
------------------------------------
Fix Version/s: 2.6.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Removed property should be considered as an environmental change
> ----------------------------------------------------------------
>
> Key: NIFI-14985
> URL: https://issues.apache.org/jira/browse/NIFI-14985
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
> Fix For: 2.6.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Let's consider the scenario:
> * I have a processor version X which is configured with properties A, B, C
> * I have a versioned flow V that contains this processor version X
> * Then I create a version Y of the processor where I now only have
> properties A and B and I did implement the _removeProperty()_ call
> If I import the flow when only the processor version Y is available, the
> versioned process group will show a local change with the property being
> removed. We should not show this as a local change since it's an expected
> modification of the flow with the call of removeProperty() (we should however
> check that this is not a dynamic property).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
