Hi Ajay, The MiNiFi docs update is still in progress for the 2.0 release. Unfortunately that part is a bit misleading: currently it is advised to use the flow.json.gz from the nifi/conf directory (unzip and copy it to minifi/conf) In https://issues.apache.org/jira/browse/NIFI-11948 the docs will be rewamped to reflect the latest changes, particularly the new flow handling mechanism.
The export flow has a bit different format, and currently not processable by MiNiFi. If you want to tailor it manually there is a 1 to 1 mapping: flowContents in the exported json is rootGroup in the flow.json.raw, externalControllerServices is controllerServices, etc It is planned to add a feature to the minifi toolkit which is able to convert exported flows to actual working flows in the final NiFi 2.0 release. You are also welcome to contribute a solution if you wish. Regards Ferenc On Wed, Jan 31, 2024 at 12:53 PM Premarajan, Ajay <ajay.premara...@intelizign.com.invalid> wrote: > Hi Team, > > We aim to integrate the most recent versions, M.2.0-M1 or M.2.0.M2, of > Apache NiFi and MiNiFi into our production environment. However, we are > encountering difficulties deploying flow files from NiFi to MiNiFi. A bug > has been reported for this issue. Please find the link below for more > details. > https://issues.apache.org/jira/browse/NIFI-12644 > > Kindly provide an estimated timeline for this issue to be addressed, or > direct me to the individual responsible for developing the module so that I > can contribute to the fixes as well. > > Regards, > Ajay Premarajan > --------------------------------------------------- > Intelizign Lifecycle Services Pvt Ltd > No.9 Murrays Gate Road (1st floor), > Alwarpet, Chennai - 600 018 > Mobile: +91-9677916373 > website: www.intelizign.com<http://www.intelizign.com> > > > DISCLAIMER: This Electronic Mail (e-mail) contains confidential and > privileged information intended only for the use of individual only for the > use of the individual or entity to which is sent. If the reader of this > message is not the intended recipient, or the employee or agent responsible > for delivery to the intended recipient, you are hereby notified that any > dissemination, distribution, or copying of this communication is STRICTLY > PROHIBITED. If you have received this communication in error, please > immediately notify the sender by reply e-mail or telephone >
