[
https://issues.apache.org/jira/browse/NIFI-8182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17275533#comment-17275533
]
Jens M Kofoed commented on NIFI-8182:
-------------------------------------
Hi [~joewitt], I'm tagging you here because I have read that a vote for NIFI
1.13.0 is started. and I think this bug I have found is a major bug in one of
the new features 1.12.0 come with. I don't know if the bug is in NIFI or in
Registry. My guess is NIFI.
I don't know if a fix is to late to make to be in the next release
Kind regard
Jens
> Single FlowFile Per Node courses bug in nested version control
> --------------------------------------------------------------
>
> Key: NIFI-8182
> URL: https://issues.apache.org/jira/browse/NIFI-8182
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.12.1
> Reporter: Jens M Kofoed
> Priority: Major
>
> I have an issue with nested PG where the root PG continuously is showing it
> has local changes but it has not.
> I have now found why, and how you can reproduce the bug
> 1. Create an empty Process Group (PG-Root)
> 2. Add version control to the PG-Root
> 3. Add an empty PG (PG-Sub) in PG-Root
> 4. Add version control to PG-Sub
> 5. Commit changes to PG-Root
> 6. Check that both PG-Root and PG-Sub are up-to-date with the green check
> mark
> 7. Change "Process Group FlowFile Concurrency" to "Single FlowFile Per
> Node" for the PG-Sub
> 8. Commit changes to PR-Sub
> 9. Refresh page
> 10. PG-Sub should have a green check mark, and PG-Root still has local
> changes
> 11. Commit changes to PG-Root
> 12. PG-Root is still showing it has local changes, but it has not.
> Bug is allso created in Nifi registry, as:
> https://issues.apache.org/jira/browse/NIFIREG-437
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
