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 <firstname.lastname@example.org> wrote:Jeff, what you are describing is in works and actively discussedand
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.
On Feb 17, 2016, at 3:08 PM, Jeff - Data Bean Australia <email@example.com> wrote:
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?
Data Bean - A Big Data Solution Provider in Australia.
--Data Bean - A Big Data Solution Provider in Australia.