[
https://issues.apache.org/jira/browse/MINIFI-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983330#comment-15983330
]
Kevin Doran commented on MINIFI-275:
------------------------------------
Confirmed issue is reproducible on macOS 10.12.4 using the following steps:
1. Clone nifi-minifi-cpp, checkout master (I was on commit
573c511f755b94eb1c6a96581ca24916585f6b8b)
2. Performed steps in README.md through `make package`
3. untar'ed nifi-minifi-cpp-0.2.0.tar.gz
4. Replaced build/nifi-minifi-cpp-0.2.0/conf/config.yml with the config.yml
file attached to this ticket (also available from
https://github.com/apache/nifi-minifi/blob/master/minifi-docs/src/main/markdown/System_Admin_Guide.md#example-config-file)
5. Attempted to run minifi via minifi.sh run and got the following output:
{code}
libc++abi.dylib: terminating with uncaught exception of type
YAML::TypedBadConversion<std::__1::basic_string<char,
std::__1::char_traits<char>, std::__1::allocator<char> > >: bad conversion
bin/minifi.sh: line 257: 5685 Abort trap: 6 ${minifi_executable}
{code}
> Configuration without IDs for components causes exceptions
> ----------------------------------------------------------
>
> Key: MINIFI-275
> URL: https://issues.apache.org/jira/browse/MINIFI-275
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: C++, Processing Configuration
> Reporter: Aldrin Piri
> Assignee: Kevin Doran
> Priority: Blocker
> Fix For: cpp-0.2.0
>
>
> One of the changes to how components are handled in C++ introduced a defect
> into the original construct over the version 1 schema of the YAML.
> The absence of this ID causes a YAML exception.
> We should provide handling to support configurations how they were created
> originally, possibly providing a default/generated ID where one isn't
> specified, and start laying the foundation for versioned schemas as provided
> in our Java implementation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
