You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Simon Bence (Jira)" <ji...@apache.org> on 2022/11/30 16:53:00 UTC
[jira] [Created] (NIFI-10914) Version information is not handled properly in case of clustered setup
Simon Bence created NIFI-10914:
----------------------------------
Summary: 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
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.
It is suspicious that the information loses during mergin in VersionControlInformationEntityMerger
--
This message was sent by Atlassian Jira
(v8.20.10#820010)