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 the 5 flows have 2 sub-flows which have a newer version. But in the 5th flow, all sub-flows is up to date. If updating the sub-flows to latest version, they continually show they need update even after updated to latest version.
Kind Regards Jens Den tor. 28. jan. 2021 kl. 07.13 skrev Jens M. Kofoed < [email protected]>: > 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 "yyyy". Local changes > have been made". > Going to show local changes, there are none listed and closing the window > a new windows popup saying: This process Group does not have any local > changes. > See attach screen dumps. > > I all so tried another group, which has neested groups with version > control. Here one of the neested groups has been changed to a newer > version. So the the new root group says there are groups which needs > update. Going to the subgroup which need updates I can see the saved > version is 3 and the newest version is 5. So I update the subgroup to lates > version. Now it still shows it needs update. Going in again for updating > the subgroup it says current version 5, newest version to select is 5. > > If have all so tried to create a new groups for all our version controlled > groups. It is only one bucket which has problems and in this bucket it is 5 > out of 11 flows which has issues. First I thought it might has something to > do with Parameter Context since this bucket is the only one where Parameter > context is used. But some of the flows which has no issues is all so using > parameter context. I'm not able to find the needle, which is in common for > only those 5 flows > > Kind regards > Jens > > > Den ons. 27. jan. 2021 kl. 17.06 skrev Bryan Bende <[email protected]>: > >> 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 10:36 AM Juan Pablo Gardella >> <[email protected]> wrote: >> > >> > Any guide that explains how a process group can be graduated to upper >> environments? >> > >> > On Wed, 27 Jan 2021 at 12:33, Joe Witt <[email protected]> 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 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 environments that they graduate properly. >> >> >> >> Thanks >> >> >> >> On Wed, Jan 27, 2021 at 8:31 AM Maksym Skrynnikov < >> [email protected]> wrote: >> >>> >> >>> 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 <[email protected]> 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 to try with the >> >>>> latest since there have been significant improvements around this >> area >> >>>> in the last few releases. >> >>>> >> >>>> On Wed, Jan 27, 2021 at 5:45 AM Jens M. Kofoed < >> [email protected]> wrote: >> >>>> > >> >>>> > Hi >> >>>> > >> >>>> > We have a situation where process groups in NIFI shows they are >> not up to date in version control. The show a *. But going to version >> control to see local changes, there are none. >> >>>> > NIFI reports back, there are no local changes. Submitting a new >> version, makes no different. A new version is created, but NIFI still shows >> the * and not the green check mark. >> >>>> > >> >>>> > I have tried to restart Registry which doesn't help. >> >>>> > >> >>>> > Restarting NIFI help for a short while. After restaring NIFI the >> process group show the green check mark and another group which is under >> the same version control now shows it needed an update. After updating the >> 2nd process group to the new version this process group now shows the * and >> not the green check mark. Going to version control to see local changes, >> there are none. >> >>>> > >> >>>> > Anybody who have experience with this issue? >> >>>> > >> >>>> > bug repport created: >> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_NIFIREG-2D437-3F&d=DwIFaQ&c=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY&r=nRtn9-9qg4PKzRb3YqAHXrLTXJYN1G0ZisUsm-XYLkObBvdpApuffGYoI9OPgBKm&m=Z9hTZ0OdCBCst-23EzCV6YNkdOQs--8BkHDlBqQlU2k&s=YVW9lyT5J-D2oUEeIGACI2vGYBHemlqdwupU_Q_5HuU&e= >> >>>> > >> >>>> > kind regards >> >>>> > >> >>>> > Jens M. Kofoed >> >
