Michael W Moser created NIFI-14442:
--------------------------------------
Summary: Conditionally show version changes in versioned flow
differences
Key: NIFI-14442
URL: https://issues.apache.org/jira/browse/NIFI-14442
Project: Apache NiFi
Issue Type: Improvement
Components: Core Framework
Reporter: Michael W Moser
Currently, if a Flow stored in a FlowRegistry uses version 2.0.0 of components,
and that Flow is imported into a NiFi version 2.3.0, the components are
automatically upgraded to 2.3.0 and the Flow is considered up-to-date. If I
make a change to the Flow and view local changes, I am not informed that the
commit would includes a version change from 2.0.0 to 2.3.0.
This issue proposes to show the version number difference as a Local Change.
We will still consider a Flow that only has "environmental changes", such as
version number, as unchanged and up-to-date. As soon as a non-environmental
change is made, then the components version number difference will be shown.
For example, if I have a Versioned Flow from NiFi 1.28.1 with GenerateFlowFile
and JSLTTransformJSON, and I make a JSLTTransformJSON property change in a NiFi
version 2.4.0, then I would see three changes:
||Component Name||Change Type||Difference||
|JSLTTransform|Property Value Changed|From 'true' to 'false'|
| |Component Bundle Changed|nifi-standard-nar version 1.28.1 to 2.4.0|
| |Component Bundle Changed|nifi-jslt-nar version 1.28.1 to 2.4.0|
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
