[jira] [Created] (MINIFI-521) minifi-toolkit-0.5.0: "Connection with id ... has invalid destination id" confused by targetId?

[Sebastian Napiorkowski (Jira)]

Sebastian Napiorkowski created MINIFI-521:
---------------------------------------------

             Summary: minifi-toolkit-0.5.0: "Connection with id ... has invalid 
destination id" confused by targetId?
                 Key: MINIFI-521
                 URL: https://issues.apache.org/jira/browse/MINIFI-521
             Project: Apache NiFi MiNiFi
          Issue Type: Bug
          Components: Agent Configuration/Installation
    Affects Versions: 0.5.0
         Environment: version: '3'
services:
  nifi:
    image: apache/nifi:latest
  minifi:
    image: apache/nifi-minifi:latest

minifi-toolkit-0.5.0, Windows
            Reporter: Sebastian Napiorkowski
         Attachments: MiNiFi-buggy.xml, MiNiFi-expected.xml, config-buggy.yml, 
config-expected.yml

I followed this tutorial: [Getting started with 
MiNiFi|https://nifi.apache.org/minifi/getting-started.html]

And the problem was that it failed with: "Connection with id 
10de7342-41ef-37a5-0000-000000000000 has invalid destination id 
9b02eb45-3c2d-3fb4-91cf-880d5038c0cd"

{code:java}
minifi-toolkit-0.5.0\bin\config.bat transform  MiNiFi-buggy.xml config-buggy.yml

There are validation errors with the template, still outputting YAML but it 
will need to be edited.
Connection with id 10de7342-41ef-37a5-0000-000000000000 has invalid destination 
id 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
{code}

By the help of brosander@github (Thank you, mate!) we discovered that the tool 
is confused by the targetId property:


{code:xml}
                    <contents>
                        <inputPorts>
                            <batchSettings/>
                            <comments></comments>
                            
<concurrentlySchedulableTaskCount>1</concurrentlySchedulableTaskCount>
                            <connected>true</connected>
                            <exists>true</exists>
                            
<groupId>db4d2e20-016e-1000-d3c7-73a67e2b1d67</groupId>
                            <id>9b02eb45-3c2d-3fb4-91cf-880d5038c0cd</id>
                            <name>input_minifi</name>
                            
<targetId>dadd7f29-016e-1000-3c91-89495c813674</targetId>
                            <targetRunning>false</targetRunning>
                            <transmitting>false</transmitting>
                            <useCompression>false</useCompression>
                        </inputPorts>
                    </contents>
{code}


when removing it, the toolkit runs through:

{code:java}
minifi-toolkit-0.5.0\bin\config.bat transform   MiNiFi-expected.xml 
config-expected.yml
No validation errors found in converted configuration.
{code}

The produced files differ:

{code:java}
diff config-buggy.yml config-expected.yml
101c101
<     - id: dadd7f29-016e-1000-3c91-89495c813674
---
>     - id: 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
{code}

I tested it and NiFi discovers MiNiFi, everything seems fine.




--
This message was sent by Atlassian Jira
(v8.3.4#803005)