Troels, At this time there is not. The flow.xml.gz file isn't meant for external usage generally and it might as well be called 'nifivoodoofiledontmesswiththis.custom'
The better answer from a version management point of view is usage of the Flow Registry and versioned flows. NiFi isn't 'design and deploy' like similar systems of the past. Rather it is interactive command and control and of course it is effectively a state machine for which we keep state (content, metadata, provenance) so we can't simply redeploy like we're starting over each time. That said we fully appreciate that folks want strong CI/CD and versioning along with that. We do increasingly make strides to optimize for such a model as well. The fundamentals there are versioned flows in the registry and parameter contexts along with the CLI. We still have more to do here but versioned flows in the registry can/should be in Git and we support JSON in that context I believe (or at the very least you can now download/upload flow definitions as JSON). For what it is worth I'll also add we routinely see user flows that are 10s of MBs even after gzip compression (or more). There are flows with 10s of thousands of processors not to mention controller services, relationships, etc.. Thanks On Thu, Jan 13, 2022 at 9:14 AM Troels Arvin <[email protected]> wrote: > > Hello, > > Is it possible to have NiFi running in a state where it uses an uncompressed > flow.xml file? - I.e. where it does not use a compressed flow.xml.gz file? > (The flow.xml files that I've seen have not been huge, so I don't quite > understand why it's compressed in the first place.) > > This is to make it easier to track changes by being able to put flow.xml > directly into Git, for example, without having to go through a (de)compress > step before putting/getting from Git. > > I didn't immediately find anything about it in the manual, so I'll try here. > > -- > Regards, > Troels Arvin
