[
https://issues.apache.org/jira/browse/NIFI-11213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Bence closed NIFI-11213.
------------------------------
> Changes in older versioned flows are not recognized when they are contained
> by other flow
> -----------------------------------------------------------------------------------------
>
> Key: NIFI-11213
> URL: https://issues.apache.org/jira/browse/NIFI-11213
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Simon Bence
> Assignee: Simon Bence
> Priority: Major
> Fix For: 2.0.0, 1.21.0
>
> Attachments: CFM-3234-TC1-INNER-version-1.json,
> CFM-3234-TC1-OUTER-version-1.json, CFM-3234-TC2-INNER-version-1.json,
> CFM-3234-TC2-OUTER-version-1.json
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> h3. Preparation steps:
> Given process group "Inner" is created and added to version control
> Given process group "Outer" is created and added to version control
> containing Inner PG as well
> h3. Actual scenario:
> Add "Outer" to the canvas from Registry
> Change something within Inner PG (rename a processor or such)
> Commit the change
> Expected behaviour:
> As "Inner" has the new version now, I would expect NiFi to show local changes
> in the Outer PG, namely the version change for Inner.
> h3. Actual behaviour:
> The actual behaviour depends on what version of NiFi was used for
> preparation. If the version contains the Registry refactoring (so 1.18.0+)
> and the snapshot is saved using storageLocation, the actual behaviour matches
> with the expected. For older NiFis (using URI to locate contained versioned
> flows) Outer will not show any changes, both PGs will be "green"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
