Hello The Flow Registry is designed to deal with challenge #1 as far as versioned flows go. For the extensions themselves you'll really want to take advantage of the nar versioning capability since versioned flows can use specific versioned extensions. Once we make an extension registry happen that will be even easier. In the mean time just merging old nars/new nars for extensions in the lib folder or another is perfectly fine.
For challenge #2 you'll need to have some sort of merge script which uses key names as a point of comparison and for new property keys you add them and for old property keys no longer present you can remove them. Generally though this is not a problem in practice as the nifi.properties have tended to port extremely well from version to version. Some vendors that do as you're describing also offer additional services using things like Apache Ambari or Cloudera Manager to help manage some of that as well. Thanks On Fri, Jan 25, 2019 at 5:49 AM Dnyaneshwar Pawar < dnyaneshwar_pa...@persistent.com> wrote: > Hi All, > > > > Help us, if anyone come across below scenario: > > > > We ship NiFi with one of our product to customer, in new release we are > planning to provide the upgrade scripts to the customer to upgrade to the > new features that we are providing through NiFi. All aspects has been > analyzed and below 2 scenarios has become pain points for us: > > > > 1. Merge flow.xml.gz: Since customer may have implemented new feature > at their end we simple can not replace our flow file. We need to retain the > customer’s changes to the flow and add our new features on top of it. > 2. Merge nifi.proeprties: for the same reason described above. (For > example. Customer may have changed HTTPS port.) > > > > Is there any inbuild utility to achieve this? > > > > Regards, > > Dnyaneshwar Pawar > > > DISCLAIMER > ========== > This e-mail may contain privileged and confidential information which is > the property of Persistent Systems Ltd. It is intended only for the use of > the individual or entity to which it is addressed. If you are not the > intended recipient, you are not authorized to read, retain, copy, print, > distribute or use this message. If you have received this communication in > error, please notify the sender and delete all copies of this message. > Persistent Systems Ltd. does not accept any liability for virus infected > mails. >
