[
https://issues.apache.org/jira/browse/NIFI-10914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17642098#comment-17642098
]
ASF subversion and git services commented on NIFI-10914:
--------------------------------------------------------
Commit 0f9541aa1e14ebf373dfe216a0b353308dd12323 in nifi's branch
refs/heads/support/nifi-1.19 from simonbence
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=0f9541aa1e ]
NIFI-10914 Adjusting input check for loading nested versioned flows (#6741)
> Version information is not handled properly in case of clustered setup
> ----------------------------------------------------------------------
>
> Key: NIFI-10914
> URL: https://issues.apache.org/jira/browse/NIFI-10914
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Simon Bence
> Assignee: Simon Bence
> Priority: Blocker
> Fix For: 1.20.0, 1.19.1
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> -When the NiFi runs in clustered mode, the already filled "statusLocation" is
> being removed from the version information after creation.-
> - During adding a flow from registry (creating a process group from the
> standpoint of NiFi) we do enrich the version control information with
> storageLocation in order to be able to be reload it from registry in case it
> will be part of a nested structure
> - This information is being added, but in case of multiple nodes, the
> information loses afterward
> It looks like, the storageLocation is empty at in thee flow.xml and flow.json
> and also it is not stored in the internal representation. Single node
> environments do not suffer from this.
> The input check for enriching version information with storageLocation needed
> a final adjustment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
