[ https://issues.apache.org/jira/browse/NIFI-10874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Witt updated NIFI-10874: ---------------------------- Fix Version/s: 1.19.1 > 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 > Fix For: 1.20.0, 1.19.1 > > 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)