Hi Greg,
WIth 1.16, NiFi expects to write out both the xml version AND the json version.
While we are in the process of making the json version the canonical version of
representing a full flow and a flow snippet, the change in 1.16 was very large
and critical to get right. So, just in case there were any bugs introduced in
the logic, we write out the flow in both the new and the old form. This way, if
there’s an issue with reading/restoring from json or writing it, users have a
way to work around it by simply deleting the .json file and loading the xml
version. Eventually, we’ll remove support for the XML version, but for now we
keep both around.
Thanks
-Mark
> On Jul 12, 2022, at 8:34 AM, Gregory M. Foreman
> wrote:
>
> Hello:
>
> My client upgraded to Nifi 1.16.1. With the original flow.xml.gz and
> autogenerated flow.json.gz in place everything works fine. When
> nifi.flow.configuration.json.file is set to the json file location and the
> original nifi.flow.configuration.file is commented out and flow.xml.gz
> removed, the server will not start. Is there any migration guidance for
> moving from flow.xml.gz to flow.json.gz?
>
> Thanks,
> Greg
