[
https://issues.apache.org/jira/browse/NIFI-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726444#comment-15726444
]
ASF GitHub Bot commented on NIFI-3138:
--------------------------------------
GitHub user brosander opened a pull request:
https://github.com/apache/nifi/pull/1304
NIFI-3138 - Adding urls, transport, proxy settings to rpg portion of …
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number
you are trying to resolve? Pay particular attention to the hyphen "-" character.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [x] Is your initial contribution a single, squashed commit?
### For code changes:
- [x] - N/A - Have you ensured that the full suite of tests is executed via
mvn -Pcontrib-check clean install at the root nifi folder?
- [x] - N/A - Have you written or updated unit tests to verify your changes?
- [x] - N/A - If adding new dependencies to the code, are these
dependencies licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [x] - N/A - If applicable, have you updated the LICENSE file, including
the main LICENSE file under nifi-assembly?
- [x] - N/A - If applicable, have you updated the NOTICE file, including
the main NOTICE file found under nifi-assembly?
- [x] - N/A - If adding new Properties, have you added .displayName in
addition to .name (programmatic access) for each of the new properties?
### For documentation related changes:
- [x] - N/A - Have you ensured that format looks appropriate for the output
in which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
…flow config xsd
Signed-off-by: Bryan Rosander <[email protected]>
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/brosander/nifi NIFI-3138
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1304.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1304
----
commit 8519642bd21211b192c2163b2de7b1b98c77fa0b
Author: Bryan Rosander <[email protected]>
Date: 2016-12-06T19:23:43Z
NIFI-3138 - Adding urls, transport, proxy settings to rpg portion of flow
config xsd
Signed-off-by: Bryan Rosander <[email protected]>
----
> 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
> Assignee: 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)
