Hey
I have found the reason to why it is not working.
to reproduce this issue:
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. Update PG-Root
6. Check that both PG-Root and PG-Sub are
I have tried to import all version flows to another NIFI server. It shows
the same picture.
kind regards
Jens
Den tor. 28. jan. 2021 kl. 07.40 skrev Jens M. Kofoed <
jmkofoed@gmail.com>:
> Hi
>
> I have tried to compare the 11 flows which is in the same bucket.
> All 11 flows is using the
Hi
I have tried to compare the 11 flows which is in the same bucket.
All 11 flows is using the same parameter context.
9 flows have nested flows which it also under version control.
All 5 flows which have issue have nested flows, but there are 4 flows with
nested flows which have no issue.
4 of
Hi Bryan
I just tried to create a new process group importing from registry. As soon
the new process group is created it show the *, and moving the cursor over
the star it says: Tracking to "xxx" Version 7 in "". Local changes have
been made".
Going to show local changes, there are none
Jens,
Is there any pattern you can identify for how to reproduce the problem?
If you were to create a brand new empty process group and start
version control, does the problem happen? is there a specific set of
steps after that which would put it into this state?
-Bryan
On Wed, Jan 27, 2021 at
Any guide that explains how a process group can be graduated to upper
environments?
On Wed, 27 Jan 2021 at 12:33, Joe Witt wrote:
> There is no requirement to use the registry. It simply gives you a way to
> store versioned flows which you can reference/use from zero or more nifi
>
There is no requirement to use the registry. It simply gives you a way to
store versioned flows which you can reference/use from zero or more nifi
clusters/flows to help keep things in line. Many teams use this to ensure
as flows are improved over time and worked through dev/test/stage/prod
We use NiFi of version 1.12.1 but we do not use NiFi Registry, I wonder if
that's the requirement to use the registry?
On Wed, Jan 27, 2021 at 2:25 PM Bryan Bende wrote:
> Please specify the versions of NiFi and NiFi Registry. If it is not
> the latest (1.12.1 and 0.8.0), then it would be good
