You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Krzysztof Zarzycki (JIRA)" <ji...@apache.org> on 2019/02/21 12:45:00 UTC
[jira] [Updated] (NIFI-6063) missing 'variable' element in
FlowConfiguration.xsd > RootProcessGroupType
[ https://issues.apache.org/jira/browse/NIFI-6063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Krzysztof Zarzycki updated NIFI-6063:
-------------------------------------
Description:
It comes up as an error when starting Nifi with existing flow.xml.gz, that uses variable on root canvas:
{code:java}
[Reconnect to Cluster] o.a.n.c.StandardFlowSynchronizer Schema validation error parsing Flow Configuration at line 121803, col 59: cvc-complex-type.2.4.a: Invalid content was found starting with element 'variable'. One of '{controllerService, template}' is expected.{code}
This is a probable cause of our issue to start nifi with existing flow.xml.gz in the cluster. We always need to delete it first before joining the cluster.
As comment above RootProcessGroupType says in FlowConfiguration.xsd , it should be almost the same as ProcessGroupType (except input/output ports) so it should allow variable element too.
was:
It comes up as an error when starting Nifi with existing flow.xml.gz, that uses variable on root canvas:
{code:java}
[Reconnect to Cluster] o.a.n.c.StandardFlowSynchronizer Schema validation error parsing Flow Configuration at line 121803, col 59: cvc-complex-type.2.4.a: Invalid content was found starting with element 'variable'. One of '{controllerService, template}' is expected.{code}
As comment above RootProcessGroupType says in FlowConfiguration.xsd , it should be almost the same as ProcessGroupType (except input/output ports) so it should allow variable element too.
> missing 'variable' element in FlowConfiguration.xsd > RootProcessGroupType
> ---------------------------------------------------------------------------
>
> Key: NIFI-6063
> URL: https://issues.apache.org/jira/browse/NIFI-6063
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.7.1
> Environment: Occured on Nifi 1.7.1, but in source code I see that it's still the case in nifi 1.9
> Reporter: Krzysztof Zarzycki
> Priority: Major
>
> It comes up as an error when starting Nifi with existing flow.xml.gz, that uses variable on root canvas:
> {code:java}
> [Reconnect to Cluster] o.a.n.c.StandardFlowSynchronizer Schema validation error parsing Flow Configuration at line 121803, col 59: cvc-complex-type.2.4.a: Invalid content was found starting with element 'variable'. One of '{controllerService, template}' is expected.{code}
> This is a probable cause of our issue to start nifi with existing flow.xml.gz in the cluster. We always need to delete it first before joining the cluster.
>
> As comment above RootProcessGroupType says in FlowConfiguration.xsd , it should be almost the same as ProcessGroupType (except input/output ports) so it should allow variable element too.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)