| Hi,
doesn’t 💯 fit your answer but maybe it is an aspect: 1) connect your old Nifi registry to a git repo (e.g. use GitHub, GitLab). 2) Push your processor groups, processors to old Nifi registry and by this it is automatically pushed to Git Repo. 3) Setup new Nifi registry and connect it to Git provider and to pushed repo. 4) After that you can pull your old code by using processor groups -> import from external repo within your Nifi
Br,
Dennis Von meinem iPhone gesendet Hello Pierre,
Thanks for new option.
So it means, the dataflow_1 register in the registry_A, will be register in the same way in registry_B after migration ?
Or needs we also use the URL aliasing ?
Regards
Hi,
the
You could also consider using the recently added Toolkit CLI optihons to export all / import all from Registry A to B.
Pierre
Hi Minh,
you could try to employ URL aliasing as explained in the docs. This way, the registry will store only an alias instead of the actual registry address. When migrating to another host, make sure to assign the same alias to it, and it should be able to retrieve versioning information properly.
Another option would be to use a persistent host name (same A/AAAA entries, or a CNAME).
This way, I have migrated our registry already a few times.
I hope this helps.
Best,
Lars
Hello all,
Someone has already migrate their nifi-registry from hostA to hostB (nifi-registry) and keep track the versionning for the nifi client points to the hostB ?
Have we got some documentations about migration nifi-registry ?
regards
Minh
|
