You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Viacheslav Kalashnikov (JIRA)" <ji...@apache.org> on 2016/12/30 15:28:58 UTC

[jira] [Created] (NIFI-3270) Transport protocol is absent in FlowConfiguration.xsd

Viacheslav Kalashnikov created NIFI-3270:
--------------------------------------------

             Summary: Transport protocol is absent in FlowConfiguration.xsd
                 Key: NIFI-3270
                 URL: https://issues.apache.org/jira/browse/NIFI-3270
             Project: Apache NiFi
          Issue Type: Bug
          Components: Core Framework
    Affects Versions: 1.0.1, 1.1.1, 1.1.0, 1.0.0
            Reporter: Viacheslav Kalashnikov


"Transport protocol" item is absent in FlowConfiguration.xsd
In case of changing RPG transport protocol from RAW to HTTP flow contains following lines:
      <remoteProcessGroup>
        <id>01591007-c243-1b2d-3434-63e135a4fd9e</id>
        <name>NiFi Flow</name>
        <position x="879.267174475651" y="1313.3869769959417"/>
        <comment/>
        <url>http://localhost:8080/nifi</url>
        <timeout>30 sec</timeout>
        <yieldPeriod>10 sec</yieldPeriod>
        <transmitting>true</transmitting>
        *{color:red}<transportProtocol>HTTP</transportProtocol>{color}*
        <proxyHost/>
        <proxyUser/>
        <inputPort>
          <id>3b3b1160-0159-1000-90c4-015947d81872</id>
          <name>notification</name>
          <position x="0.0" y="0.0"/>
          <comments/>
          <scheduledState>RUNNING</scheduledState>
          <maxConcurrentTasks>1</maxConcurrentTasks>
          <useCompression>false</useCompression>
        </inputPort>
      </remoteProcessGroup>

However mentioned item is absent in /nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/resources/FlowConfiguration.xsd
Its structure is:
 190     <xs:complexType name="RemoteProcessGroupType">
 191         <xs:sequence>
 192             <xs:element name="id" type="NonEmptyStringType" />
 193             <xs:element name="name" type="xs:string" />
 194             <xs:element name="position" type="PositionType" />
 195             <xs:element name="comment" type="xs:string" />
 196             <xs:element name="url" type="xs:anyURI" />
 197             <xs:element name="timeout" type="xs:string" />
 198             <xs:element name="yieldPeriod" type="TimePeriod" minOccurs="0" maxOccurs="1" />
 199             <xs:element name="transmitting" type="xs:boolean" />
 200             {color:green}* it should be here*{color}
 201             <!-- The input ports and output ports of the remote group may change without our knowledge; however,
 202             they are persisted here because on a restart of NiFi, we need to have the Input & Output Ports' IDs
 203             and associated names persisted so that we can attempt to connect to these ports -->
 204             <xs:element name="inputPort" type="RemoteGroupPortType" minOccurs="0" maxOccurs="unbounded" />
 205             <xs:element name="outputPort" type="RemoteGroupPortType" minOccurs="0" maxOccurs="unbounded" />
 206         </xs:sequence>
 207     </xs:complexType>

This absence produces error in logs on NiFi starting. Looks like it has no inluence on flow operability. But from perspective of amount of logged errors it is not so good as expected 



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