You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Matt Burgess (Jira)" <ji...@apache.org> on 2021/04/28 15:59:03 UTC
[jira] [Updated] (MINIFI-521) minifi-toolkit-0.5.0: "Connection
with id ... has invalid destination id" confused by targetId?
[ https://issues.apache.org/jira/browse/MINIFI-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Burgess updated MINIFI-521:
--------------------------------
Fix Version/s: (was: 0.6.0)
1.14.0
> 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:1:10.0
> minifi:
> image: apache/nifi-minifi:0.5.0
> minifi-toolkit-0.5.0, Windows
> Reporter: Sebastian Napiorkowski
> Assignee: Aldrin Piri
> Priority: Minor
> Fix For: 1.14.0
>
> Attachments: MiNiFi-buggy.xml, MiNiFi-expected.xml, config-buggy.yml, config-expected.yml, config.yml, minifi-flow.xml
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> I followed this tutorial: [Getting started with MiNiFi|https://nifi.apache.org/minifi/getting-started.html]
> And the problem was that, while transforming the Template to the yml-file, 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}
> just by removing the {{targetId}}, 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.-
> EDIT:
> I celebrated to early. Removing the {{targetId}} is *not* a working workaround. The easiest way to get around this issue is to downgrade NiFi from 1.10 to 1.9.2.
> Originally I thought this is a MiNiFi issue, but now I'm thinking that something changed in NiFi from 1.9.2 to 1.10.0 when exporting Templates. The ids are mixed up. This could be a much more critical bug, than I initially thought.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)