Josef Zahner created NIFI-15841:
-----------------------------------
Summary: Nested NiFi Registry Flows requires always fully
committed child PGs
Key: NIFI-15841
URL: https://issues.apache.org/jira/browse/NIFI-15841
Project: Apache NiFi
Issue Type: Bug
Affects Versions: 2.9.0
Reporter: Josef Zahner
Attachments: image-2026-04-15-16-46-33-257.png,
image-2026-04-15-16-52-54-766.png
# If there is a change on "Child PG", a change on "Parent PG" and we would like
to commit the flow on the Parent PG (of course without the changes in "Child
PG"), we can't commit it due to this screen -> not good, we often work in a way
that we have changes in some of the Child PGs, but we would like to commit only
the "Parent PG" and some of the already committed "Child PG"s. With NiFi 2.9.0
we can't do that anymore. Everything on all the "PG Child"s has to be committed
first, before we can commit the Parent PG.
!image-2026-04-15-16-46-33-257.png!
# The same for reverting a change. We can't revert changes on "PG Parent", if
there are changes in "PG Child". We get the following error in the bottom of
the screenshot. The revert on "PG Parent" should be independent of the PG
Child. Today, you are forced to commit the "PG Child", to be able to revert "PG
Parent".
!image-2026-04-15-16-52-54-766.png!
It's not convenient to commit first the "Child PG" to do any changes on the
"Parent PG". It should be independent, as it has anyway it's own commit. "PG
Parent" should track only the versions from "PG Child" nothing else. If the
version of "PG Child" matches to the one of "Parent PG", it should allow
commit/revert, even though there are uncommitted "PG Child" parts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
