[
https://issues.apache.org/jira/browse/NIFI-10016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-10016.
-----------------------------------
Resolution: Feedback Received
Apache NiFi 1.x is no longer maintained and no new release is planned on the
1.x release line. Marking as resolved as part of a cleanup operation. Please
open a new one with an updated description if this is still relevant for NiFi
2.x.
> Unannounced change to flow.json.gz
> ----------------------------------
>
> Key: NIFI-10016
> URL: https://issues.apache.org/jira/browse/NIFI-10016
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Documentation & Website
> Affects Versions: 1.16.0, 1.16.1
> Reporter: Daniel Salwerowicz
> Priority: Trivial
> Attachments: 2022-05-11--12-35-22.png, 2022-05-11--12-37-29.png
>
>
> As far as I am aware there is no information anywhere that flow.xml.gz is now
> being replaced by flow.json.gz.
> While it might not be that big of a deal to some I was very concerned that
> neither changelog, nor migration guide from 1.15 to 1.16 mention that this
> has occurred.
> The only way I noticed that was because during update I needed to look up
> something in nifi.properties file and noticed a configuration option for
> flow.json.gz.
> This lead me to search for what it is, when the change happened etc.
> The only place in documentation where I can see flow.json.gz being mentioned
> is in the Admin Guide, which itself pulled a move comparable to ministry of
> truth from 1984 and just acts like flow.json.gz was always used in NiFi, no
> mention about change or what to do with old flow.xml.gz files.
> I think that both changelog and migration guide should at the very least
> mention that switch to flow.json.gz has occured, why it happened, and how to
> deal with old flow.xml.gz when upgrading.
> If I am wrong and there is mention of flow.json.gz anywhere in the official
> channels, then I apologize, and ask for link to them so I can read more.
> It was very surprising to come across it when I wasn't expecting it after
> reading both changelog and migration guide.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
