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<std::string>'
>   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-0000-000000000000 (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

Reply via email to