[jira] [Commented] (MINIFI-147) MiNiFi C++ startup error due to property name mismatch in config.yml
[
https://issues.apache.org/jira/browse/MINIFI-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15939449#comment-15939449
]
marco polo commented on MINIFI-147:
---
Hi [~ijokarumawak], are you seeking an improvement in the toolkit or better
error messages for the user? Based on previous responses I'm betting the
former. Is there anything else to do for this ticket? Thanks!
> MiNiFi C++ startup error due to property name mismatch in config.yml
>
>
> Key: MINIFI-147
> URL: https://issues.apache.org/jira/browse/MINIFI-147
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: C++
>Affects Versions: cpp-0.1.0
>Reporter: Koji Kawamura
>
> A config.yml file created by minifi-toolkit-0.1.0 "config.sh transform"
> command causes following MiNiFi C++ startup error due to several naming
> mismatch between MiNiFi C++ and minifi-toolkit.
> {code}
> pi@raspberrypi:~/dev/nifi-minifi-cpp-0.1.0 $ terminate called after throwing
> an instance of 'YAML::TypedBadConversion'
> what(): bad conversion
> {code}
> I had to modify generated conf.yml as below to start MiNiFi C++:
> * Connections:
> ** source name: TailFile (cpp expects)
> ** source id: b9340f85-0158-1000-- (toolkit generated)
> ** source relationship name: success (cpp)
> ** source relationship names: - success (toolkit generated array)
> ** destination name: b52ba2de-0158-1000-fda0-5861ac7dbb2f (cpp)
> ** destination id: b52ba2de-0158-1000-fda0-5861ac7dbb2f (toolkit)
> * Remote Processing Groups (cpp)
> * Remote Process Groups (toolkit)
> ** Port and Host properties for Input Ports are also added manually to start
> MiNiFi, but this is documented properly.
> MINIFI-137 has changed constant name. We need to check if such change affects
> MiNiFi C++ as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MINIFI-147) MiNiFi C++ startup error due to property name mismatch in config.yml
[
https://issues.apache.org/jira/browse/MINIFI-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712171#comment-15712171
]
Aldrin Piri commented on MINIFI-147:
I think we can establish a matrix of compatibility with the toolkits and can
accompany some documentation concerning schema versions (a changelog of sorts).
Will create a ticket for establishing that and link here.
> MiNiFi C++ startup error due to property name mismatch in config.yml
>
>
> Key: MINIFI-147
> URL: https://issues.apache.org/jira/browse/MINIFI-147
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: C++
>Affects Versions: cpp-0.1.0
>Reporter: Koji Kawamura
>
> A config.yml file created by minifi-toolkit-0.1.0 "config.sh transform"
> command causes following MiNiFi C++ startup error due to several naming
> mismatch between MiNiFi C++ and minifi-toolkit.
> {code}
> pi@raspberrypi:~/dev/nifi-minifi-cpp-0.1.0 $ terminate called after throwing
> an instance of 'YAML::TypedBadConversion'
> what(): bad conversion
> {code}
> I had to modify generated conf.yml as below to start MiNiFi C++:
> * Connections:
> ** source name: TailFile (cpp expects)
> ** source id: b9340f85-0158-1000-- (toolkit generated)
> ** source relationship name: success (cpp)
> ** source relationship names: - success (toolkit generated array)
> ** destination name: b52ba2de-0158-1000-fda0-5861ac7dbb2f (cpp)
> ** destination id: b52ba2de-0158-1000-fda0-5861ac7dbb2f (toolkit)
> * Remote Processing Groups (cpp)
> * Remote Process Groups (toolkit)
> ** Port and Host properties for Input Ports are also added manually to start
> MiNiFi, but this is documented properly.
> MINIFI-137 has changed constant name. We need to check if such change affects
> MiNiFi C++ as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MINIFI-147) MiNiFi C++ startup error due to property name mismatch in config.yml
[
https://issues.apache.org/jira/browse/MINIFI-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712138#comment-15712138
]
Aldrin Piri commented on MINIFI-147:
More work with little reward, of course! Your suggestion is completely the
right one. I like when we can solve things with doc patches! :)
> MiNiFi C++ startup error due to property name mismatch in config.yml
>
>
> Key: MINIFI-147
> URL: https://issues.apache.org/jira/browse/MINIFI-147
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: C++
>Affects Versions: cpp-0.1.0
>Reporter: Koji Kawamura
>
> A config.yml file created by minifi-toolkit-0.1.0 "config.sh transform"
> command causes following MiNiFi C++ startup error due to several naming
> mismatch between MiNiFi C++ and minifi-toolkit.
> {code}
> pi@raspberrypi:~/dev/nifi-minifi-cpp-0.1.0 $ terminate called after throwing
> an instance of 'YAML::TypedBadConversion'
> what(): bad conversion
> {code}
> I had to modify generated conf.yml as below to start MiNiFi C++:
> * Connections:
> ** source name: TailFile (cpp expects)
> ** source id: b9340f85-0158-1000-- (toolkit generated)
> ** source relationship name: success (cpp)
> ** source relationship names: - success (toolkit generated array)
> ** destination name: b52ba2de-0158-1000-fda0-5861ac7dbb2f (cpp)
> ** destination id: b52ba2de-0158-1000-fda0-5861ac7dbb2f (toolkit)
> * Remote Processing Groups (cpp)
> * Remote Process Groups (toolkit)
> ** Port and Host properties for Input Ports are also added manually to start
> MiNiFi, but this is documented properly.
> MINIFI-137 has changed constant name. We need to check if such change affects
> MiNiFi C++ as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MINIFI-147) MiNiFi C++ startup error due to property name mismatch in config.yml
[
https://issues.apache.org/jira/browse/MINIFI-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712076#comment-15712076
]
Bryan Rosander commented on MINIFI-147:
---
[~aldrin] currently the old version code in the toolkit is more concerned with
upgrading and validating than outputing old versions. We could add that
capability but it would increase the complexity (now we're talking about
keeping around the old logic for transforming the template xml to config yml,
not just validating and upgrading the yml itself).
I'm wondering what that buys us over specifying that the 0.0.1 toolkit is to be
used with this version of MiNiFi cpp.
> MiNiFi C++ startup error due to property name mismatch in config.yml
>
>
> Key: MINIFI-147
> URL: https://issues.apache.org/jira/browse/MINIFI-147
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: C++
>Affects Versions: cpp-0.1.0
>Reporter: Koji Kawamura
>
> A config.yml file created by minifi-toolkit-0.1.0 "config.sh transform"
> command causes following MiNiFi C++ startup error due to several naming
> mismatch between MiNiFi C++ and minifi-toolkit.
> {code}
> pi@raspberrypi:~/dev/nifi-minifi-cpp-0.1.0 $ terminate called after throwing
> an instance of 'YAML::TypedBadConversion'
> what(): bad conversion
> {code}
> I had to modify generated conf.yml as below to start MiNiFi C++:
> * Connections:
> ** source name: TailFile (cpp expects)
> ** source id: b9340f85-0158-1000-- (toolkit generated)
> ** source relationship name: success (cpp)
> ** source relationship names: - success (toolkit generated array)
> ** destination name: b52ba2de-0158-1000-fda0-5861ac7dbb2f (cpp)
> ** destination id: b52ba2de-0158-1000-fda0-5861ac7dbb2f (toolkit)
> * Remote Processing Groups (cpp)
> * Remote Process Groups (toolkit)
> ** Port and Host properties for Input Ports are also added manually to start
> MiNiFi, but this is documented properly.
> MINIFI-137 has changed constant name. We need to check if such change affects
> MiNiFi C++ as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MINIFI-147) MiNiFi C++ startup error due to property name mismatch in config.yml
[
https://issues.apache.org/jira/browse/MINIFI-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712045#comment-15712045
]
Aldrin Piri commented on MINIFI-147:
Hi Koji,
Thanks for reporting. We can certainly provide better error handling in C++.
Could you specify your environment on which you experienced this? The way the
program can error can vary between platforms and OS.
[~bryanrosan...@gmail.com] At the core of this, I think we should consider
allowing a specification of version in the toolkit. Given that the C++ version
trails the Java one, the supported config schema will also lag on any changes
in Java. Thoughts?
> MiNiFi C++ startup error due to property name mismatch in config.yml
>
>
> Key: MINIFI-147
> URL: https://issues.apache.org/jira/browse/MINIFI-147
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: C++
>Affects Versions: 0.1.0
>Reporter: Koji Kawamura
>
> A config.yml file created by minifi-toolkit-0.1.0 "config.sh transform"
> command causes following MiNiFi C++ startup error due to several naming
> mismatch between MiNiFi C++ and minifi-toolkit.
> {code}
> pi@raspberrypi:~/dev/nifi-minifi-cpp-0.1.0 $ terminate called after throwing
> an instance of 'YAML::TypedBadConversion'
> what(): bad conversion
> {code}
> I had to modify generated conf.yml as below to start MiNiFi C++:
> * Connections:
> ** source name: TailFile (cpp expects)
> ** source id: b9340f85-0158-1000-- (toolkit generated)
> ** source relationship name: success (cpp)
> ** source relationship names: - success (toolkit generated array)
> ** destination name: b52ba2de-0158-1000-fda0-5861ac7dbb2f (cpp)
> ** destination id: b52ba2de-0158-1000-fda0-5861ac7dbb2f (toolkit)
> * Remote Processing Groups (cpp)
> * Remote Process Groups (toolkit)
> ** Port and Host properties for Input Ports are also added manually to start
> MiNiFi, but this is documented properly.
> MINIFI-137 has changed constant name. We need to check if such change affects
> MiNiFi C++ as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
