[NIFI-10874] Multiple levels of versioned flows might not able to load from repository

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.20.0, 1.19.1
• Component/s: Core Framework
• Assignee: Simon Bence
• Reporter: Simon Bence
• Created: 24/Nov/22 15:44
• Updated: 30/Nov/22 19:53
• Resolved: 28/Nov/22 16:45

Description

With the refactoring of the registry (changing it to a component), several necessary change was done, including the "generification" of the way included versioned flows are handled (recognised).

Previous implementation was depending on an URI, which was not descriptive enough for the new concept. Storage location has been introduced and now registry client implementations are capable for determine if they are capable to load a given flow based on this.

As a fallback mechanism, the URI was kept for the NiFiRegistry based implementation. A bug has been introduced with this mechanism, namely: the ProcessGroupResouce#createProcessGroup method works with version information from the UI, which has no knowledge of this. In order to guarantee that the given information is stored during flow creation (here: loading flow from external source) we need to guarantee the transition of this information.

Issue Links

• links to: GitHub Pull Request #6719