You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/11/10 17:25:11 UTC
[jira] [Commented] (NIFI-1024) Fix Mistake in Clustering section of
Admin Guide
[ https://issues.apache.org/jira/browse/NIFI-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998858#comment-14998858 ]
ASF GitHub Bot commented on NIFI-1024:
--------------------------------------
GitHub user olegz opened a pull request:
https://github.com/apache/nifi/pull/119
NIFI-1024 NIFI-1062 Fixed PutHDFS processor to properly route failures.
Ensured that during put failures the FlowFile is routed to 'failure' relationship.
Added validation test
Re-enabled previously ignored test.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/olegz/nifi NIFI-1124
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/119.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 #119
----
commit d10befd4647e7c7456d3d85809b280ab3ac087dc
Author: Oleg Zhurakousky <ol...@suitcase.io>
Date: 2015-11-10T12:58:28Z
NIFI-1024 NIFI-1062 Fixed PutHDFS processor to properly route failures.
Ensured that during put failures the FlowFile is routed to 'failure' relationship.
Added validation test
Re-enabled previously ignored test.
----
> Fix Mistake in Clustering section of Admin Guide
> ------------------------------------------------
>
> Key: NIFI-1024
> URL: https://issues.apache.org/jira/browse/NIFI-1024
> Project: Apache NiFi
> Issue Type: Task
> Components: Documentation & Website
> Affects Versions: 0.3.0
> Reporter: Jennifer Patricia Barnabee
> Assignee: Aldrin Piri
> Priority: Minor
>
> In the Clustering section of the Admin Guide, the instructions mistakenly reference "nifi.cluster.protocol.manager.port", but it should say "nifi.cluster.manager.protocol.port". This should be fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)