You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2017/11/28 15:10:00 UTC
[jira] [Updated] (MINIFI-348) Schema validation error parsing Flow
Configuration
[ https://issues.apache.org/jira/browse/MINIFI-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph Witt updated MINIFI-348:
-------------------------------
Fix Version/s: 0.3.0
> Schema validation error parsing Flow Configuration
> --------------------------------------------------
>
> Key: MINIFI-348
> URL: https://issues.apache.org/jira/browse/MINIFI-348
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Processing Configuration
> Affects Versions: 0.2.0
> Environment: Rasbian Jessie (current version)
> Reporter: Nathan Green
> Assignee: Aldrin Piri
> Priority: Minor
> Fix For: 0.3.0
>
> Attachments: EdgeCollect.xml, config.yml, flow.xml, minifi-app.log, minifi-bootstrap.log
>
>
> Using Minifi 0.2.0 Java for a project using Raspberry Pi's.
> Have created a simple flow in NIFI, saved template and exported then converted to yaml using the Minifi Toolkit 0.2.0. Validation of the template passes.
> When executing Minifi, get the following warning in the log:
> 2017-07-10 09:45:34,671 WARN [main] o.a.n.c.StandardFlowSynchronizer Schema validation error parsing Flow Configuration at line 17, col 27: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
> 2017-07-10 09:45:34,692 WARN [main] o.a.n.c.StandardFlowSynchronizer Schema validation error parsing Flow Configuration at line 79, col 27: cvc-complex-type.2.4.a: Invalid content was found starting with element 'maxConcurrentTasks'. One of '{bundle}' is expected.
> Files attached: EdgeCollect.xml - exported template from Nifi
> config.yml - the yaml config generated by toolkit (some minor manual edits)
> flow.xml - Minifi created flow.xml file
> *.log - log files from minifi server
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)