[
https://issues.apache.org/jira/browse/NIFI-12644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17812693#comment-17812693
]
Ferenc Erdei commented on NIFI-12644:
-------------------------------------
Designing a whole flow and putting it under MiNiFi works as it was designed.
The goal there was to use the same flow.json format as NiFi use (not the one
that can be exported from the UI).
If I understand correctly you'd need to export a json of a process group and
transform it to a format that MiNiFi can read. I feel that is a new feature
requirement rather than a bug.
> Exported json flows does not match minifi json schema
> -----------------------------------------------------
>
> Key: NIFI-12644
> URL: https://issues.apache.org/jira/browse/NIFI-12644
> Project: Apache NiFi
> Issue Type: Bug
> Components: MiNiFi
> Affects Versions: 2.0.0-M1
> Reporter: Valiantsin Shukaila
> Priority: Major
> Attachments: flow-exported-from-nifi2.json,
> minifi-example-flow-from-tests.json
>
>
> In documentation for Minifi java agent project it is mentioned that in order
> to import process flow, now it is necessary to export nifi flow as json and
> put it in minifi. here link to doc:
> [https://github.com/apache/nifi/blob/main/minifi/minifi-docs/src/main/markdown/minifi-java-agent-quick-start.md]
> But in fact the JSON formats compeltelly do not match. Minifi expect format
> of legacy nifi flow templates just in JSON. But exported nifi flows is
> something very much different.
> Therefore it is not really possible to import flows from nifi-2.0 version to
> minifi 2.0 version.
> It is only possible to export template from nifi 1.2.x version and convert it
> into json format for minifi-2.0 version.
> for file differences please see attached files.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
