[ 
https://issues.apache.org/jira/browse/NIFI-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bryan Rosander updated NIFI-3138:
---------------------------------
    Description: 
There are new valid elements in the Remote Process Group portion of the 
[standard flow serializer 
xml|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/serialization/StandardFlowSerializer.java#L253].
  These are currently not part of the 
[xsd|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/resources/FlowConfiguration.xsd#L200].

This means that if these elements are in the flow.xml, you get output like the 
following (from MiNiFi but it's using the [1.1.0 NiFi core 
libraries|https://github.com/apache/nifi-minifi/commit/85d69eadae5bffb570a28fcb4a05649d58605ce6]):
{code}
2016-12-01 19:22:24,850 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,890 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,909 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,927 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,974 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,992 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
{code}

The flow still seems to work so I think it's just a warning but still not great 
to see in the logs.

  was:
There are new valid elements in the Remote Process Group portion of the 
[standard flow serializer 
xml|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/serialization/StandardFlowSerializer.java#L253].
  These are currently not part of the 
[xsd|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/resources/FlowConfiguration.xsd#L200].

This means that if these elements are in the flow.xml, you get output like the 
following (from MiNiFi but it's using the 1.1.0 NiFi core libraries):
{code}
2016-12-01 19:22:24,850 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,890 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,909 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,927 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,974 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,992 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
{code}

The flow still seems to work so I think it's just a warning but still not great 
to see in the logs.


> Need to add new RPG elements to FlowConfiguration.xsd
> -----------------------------------------------------
>
>                 Key: NIFI-3138
>                 URL: https://issues.apache.org/jira/browse/NIFI-3138
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>            Reporter: Bryan Rosander
>            Priority: Minor
>         Attachments: InvokeHttpMiNiFiTemplateTest.xml, config.yml, flow.xml.gz
>
>
> There are new valid elements in the Remote Process Group portion of the 
> [standard flow serializer 
> xml|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/serialization/StandardFlowSerializer.java#L253].
>   These are currently not part of the 
> [xsd|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/resources/FlowConfiguration.xsd#L200].
> This means that if these elements are in the flow.xml, you get output like 
> the following (from MiNiFi but it's using the [1.1.0 NiFi core 
> libraries|https://github.com/apache/nifi-minifi/commit/85d69eadae5bffb570a28fcb4a05649d58605ce6]):
> {code}
> 2016-12-01 19:22:24,850 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,890 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,909 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,927 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,974 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,992 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> {code}
> The flow still seems to work so I think it's just a warning but still not 
> great to see in the logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to