[
https://issues.apache.org/jira/browse/NIFI-10874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17640133#comment-17640133
]
ASF subversion and git services commented on NIFI-10874:
--------------------------------------------------------
Commit df2147829742129c039b37c5d6f4f11aa54785a2 in nifi's branch
refs/heads/main from Simon Bence
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=df21478297 ]
NIFI-10874 Fixed issue with multiple levels of versioned flows
This closes #6719
Signed-off-by: David Handermann <[email protected]>
> Multiple levels of versioned flows might not able to load from repository
> -------------------------------------------------------------------------
>
> Key: NIFI-10874
> URL: https://issues.apache.org/jira/browse/NIFI-10874
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Simon Bence
> Assignee: Simon Bence
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
