My team has played around with versioning control with the nifi in the following way (we have yet to use this for deployments yet though):
- We version control the flow.xml file and all of the config files that need to be changed - We build a distribution of nifi, gziping the flow.xml and string-replacing properties in the config files with maven - We then can install this "version" of our nifi app. We want to be able to use this to test our flows and processes on our test system before making it live in production. But like I said he have yet to actually use this for production deployments. On Wed, Feb 17, 2016 at 7:21 PM, Jeff - Data Bean Australia < databean...@gmail.com> wrote: > Thanks Matt for describing the feature in such an intuitive way, and > pointing out the location for the archive. > > This looks good. Just wondering whether we also want to archive the > templates along with flow.xml.gz. > > Thanks, > Jeff > > On Thu, Feb 18, 2016 at 11:08 AM, Matthew Clarke < > matt.clarke....@gmail.com> wrote: > >> Jeff, >> NiFi gives users the ability to create snapshot backups of their >> flow.xml through the "back-up flow" link found under the "controller >> settings" (Icon looks like wrench and screwdriver in upper right corner). >> The default nifi.properties configuration will write these back-ups to a >> directory called archive inside teh <nifi-root-install>/conf directory, but >> you can of course change were they are written. >> >> Matt >> >> On Wed, Feb 17, 2016 at 4:52 PM, Jeff - Data Bean Australia < >> databean...@gmail.com> wrote: >> >>> Thanks Oleg for sharing this. They are definitely useful. >>> >>> By my question focused more on keeping the data flow definition files' >>> versions, so that Data Flow Developers, or NiFi Cluster Manager in NiFi's >>> term can keep track of our work. >>> >>> Currently I am using the following command line to generate a formatted >>> XML to put it into our Git repository: >>> >>> cat conf/flow.xml.gz | gzip -dc | xmllint --format - >>> >>> >>> >>> >>> On Thu, Feb 18, 2016 at 10:01 AM, Oleg Zhurakousky < >>> ozhurakou...@hortonworks.com> wrote: >>> >>>> Jeff, what you are describing is in works and actively discussed >>>> https://cwiki.apache.org/confluence/display/NIFI/Extension+Registry >>>> and >>>> >>>> https://cwiki.apache.org/confluence/display/NIFI/Component+documentation+improvements >>>> >>>> The last one may not directly speaks to the “ExtensionRegistry”, but if >>>> you look through he comments there is a whole lot about it since it is >>>> dependent. >>>> Feel free to participate, but I can say for now that it is slated for >>>> 1.0 release. >>>> >>>> Cheers >>>> Oleg >>>> >>>> On Feb 17, 2016, at 3:08 PM, Jeff - Data Bean Australia < >>>> databean...@gmail.com> wrote: >>>> >>>> Hi, >>>> >>>> As my NiFi data flow becomes more and more serious, I need to put on >>>> Version Control. Since flow.xml.gz is generated automatically and it is >>>> saved in a compressed file, I am wondering what would be the best practice >>>> regarding version control? >>>> >>>> Thanks, >>>> Jeff >>>> >>>> -- >>>> Data Bean - A Big Data Solution Provider in Australia. >>>> >>>> >>>> >>> >>> >>> -- >>> Data Bean - A Big Data Solution Provider in Australia. >>> >> >> > > > -- > Data Bean - A Big Data Solution Provider in Australia. >
