[
https://issues.apache.org/jira/browse/MINIFI-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15440521#comment-15440521
]
ASF subversion and git services commented on MINIFI-84:
-------------------------------------------------------
Commit ce3d3e49892554e512fe0f68f99c5d413c8d5535 in nifi-minifi-cpp's branch
refs/heads/master from [~aldrin]
[ https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;h=ce3d3e4 ]
MINIFI-84 Performing explicit checking on values of processor Properties YAML.
An empty value is treated as a YAML node in lieu of being null and would lead
to conversion errors.
This closes #7.
> nifi-minifi-cpp flow.yml startup errors
> ---------------------------------------
>
> Key: MINIFI-84
> URL: https://issues.apache.org/jira/browse/MINIFI-84
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: C++, Processing Configuration
> Reporter: Randy Gelhausen
> Assignee: Aldrin Piri
> Fix For: cpp-0.0.1
>
> Attachments: MiNiFi-Flow.xml, flow.yml
>
>
> Using a recent NiFi 1.0 build, I created a template with GetFile and TailFile
> gathering data and pushing it to a Remote Process Group.
> After exporting the template, I used nifi-minifi's minifi-toolkit to convert
> the XML into a yaml flow definition.
> On attempting to start nifi-minifi-cpp with the flow.yml generated by
> minifi-toolkit, I get 'YAML::TypedBadConversion<std::string>' errors.
> Attached are the template & flow.yml. Below are the mini-toolkit converter
> and minifi logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
