Thank you very much for your reply Bryan. I will look into the page you suggested.
On Thu, Dec 15, 2016 at 9:24 AM, Bryan Bende <[email protected]> wrote: > James, > > The short answer is that everything you described should be possible, and > upgrading from 0.6.1 to 0.7 should be straight forward. > > 1) Yes you can copy the flow.xml.gz from one instance to the other. This > files doesn't actually hold any information about the data, that is all > held in the repositories, the flow.xml only holds the definition of the > flow (what processors/groups there are, how they are connected etc). The > state of the flow in terms of where data is would be based on the flow file > repository. > > 2) Yes you should be able to point at the same repos. The 0.x baselines > does not incorporate any version info in the repositories as far as I know, > so I believe you can go back and forth between 0.6 and 0.7, but in the 1.1 > release there was something introduced that I believe would make it so you > can't go back from 1.1 to 1.0, but helps will rollbacks going forward after > 1.1 (https://issues.apache.org/jira/browse/NIFI-2854) > > 3) I don't know of anything that changed for 0.7 related to this. > > 4) You should be able to use the same certs and keys. > > This page is a little bit old, but it has some additional info that might > be worth reading regarding upgrading: > https://cwiki.apache.org/confluence/display/NIFI/Upgrading+NiFi > > Thanks, > > Bryam > > > On Thu, Dec 15, 2016 at 6:49 AM, James McMahon <[email protected]> > wrote: > >> NiFi 0.6.1 was the first NiFi baseline I installed in my local data >> enterprise. I now find that there are refinements in v0.7 that I require, >> and so I must install/upgrade my NiFi baseline. I've never done this and >> need to better understand the steps required to properly upgrade. >> >> I have a base dir named /home/nifi. Under that I have a nifi-061 >> subdirectory for that code and configuration baseline. I intend to install >> 0.7 in a nifi-07 subdirectory. I use a soft link in /home/nifi (called >> latest) to point at the current version for my system. >> >> Q1: My 0.6.1 baseline has a complex workflow that I don't want to rebuild >> from scratch in the nifi07/conf subdirectory. Assuming that I first flush >> all my queues and gracefully shutdown my 0.6.1 instance, am I permitted to >> simply copy my 0.6.1 flow.xml.gz into my nifi07/conf subdirectory to have >> my expansive workflow present in the nifi UI when I start my new 0.7 >> installation? >> >> Q2: On my system I currently have distributed my flow_repo, content_repo, >> and provenance_repo to different independent mounted disk devices available >> to me. I did this to optimize my opportunity to recover in case of >> unanticipated system failures. Can I use the same repos for my 0.7 >> installation, referencing them in my conf/nifi.properties file just as I >> did for my 0.6.1 baseline? Is NiFi differentiating by version the records >> it persists in these repositories? Or once I commit to the new version, >> there's no going back to the previous version because the repos save >> objects without any reference to nifi version instance? >> >> Q3: My 0.6.1 instance starts at system boot time as a service. Are you >> aware of any specific elements in the service configuration that must >> change in order to start the new version similarly as a service? >> >> Q4: My 0.6.1 instance leverages certificates and a key store to establish >> a secure nifi instance. As such my nifi version directory has a keys >> subdirectory (and a certs subdirectory under that). When I migrate to the >> new version, am I permitted to just copy those subdirectories under my new >> nifi07 directory? Are there any other considerations in order to maintain >> secure authentication and secure http operations in my workflow? >> >> Q5: In your experience are there any other hurdles when upgrading nifi to >> a new version that I am overlooking? >> >> Thank you in advance for any insights you can offer. >> > >
