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/08/19 06:38:45 UTC
[jira] [Commented] (NIFI-868) Configure advertised host name of
Remote Process Group Input Port
[ https://issues.apache.org/jira/browse/NIFI-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14702431#comment-14702431 ]
ASF GitHub Bot commented on NIFI-868:
-------------------------------------
GitHub user pukkaone opened a pull request:
https://github.com/apache/nifi/pull/74
NIFI-868 Configure advertised host name of Remote Process Group Input…
… Port
Before this change, the host given out to clients to connect to a Remote
Process Group Input Port is the host where the NiFi instance runs.
However, sometimes the binding host is different from the host that
clients connect to. For example, when a NiFi instance runs inside a
Docker container, a client on a separate machine must connect to the
Docker host which forwards the connection to the container.
Kafka addresses this situation by allowing a broker to configure the
host name given out to producers, consumers, and other brokers to connect to.
Implement something similar in NiFi.
Add a configuration property to specify the host name to give out to
clients to connect to a Remote Process Group Input Port. If the property
is not configured, then give out the name of host running the NiFi
instance.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pukkaone/nifi nifi-868
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/74.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 #74
----
commit 8f98f8093868e0ed2fb1dfbe3947f1afc1bdd10b
Author: Chin Huang <pu...@gmail.com>
Date: 2015-08-19T02:35:25Z
NIFI-868 Configure advertised host name of Remote Process Group Input Port
Before this change, the host given out to clients to connect to a Remote
Process Group Input Port is the host where the NiFi instance runs.
However, sometimes the binding host is different from the host that
clients connect to. For example, when a NiFi instance runs inside a
Docker container, a client on a separate machine must connect to the
Docker host which forwards the connection to the container.
Add a configuration property to specify the host name to give out to
clients to connect to a Remote Process Group Input Port. If the property
is not configured, then give out the name of host running the NiFi
instance.
----
> Configure advertised host name of Remote Process Group Input Port
> -----------------------------------------------------------------
>
> Key: NIFI-868
> URL: https://issues.apache.org/jira/browse/NIFI-868
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 0.2.1
> Environment: Linux
> Reporter: Chin Huang
>
> The host given out to clients to connect to a Remote Process Group Input Port is the host where the NiFi instance runs. However, sometimes the binding host is different from the host that clients connect to. For example, when a NiFi instance runs inside a Docker container, a client on a separate machine must connect to the Docker host which forwards the connection to the container.
> Kafka addresses this situation by allowing a broker to configure the host name given out to producers, consumers, and other brokers to connect to. Implement something similar in NiFi. Add a configuration property to specify the host name to give out to clients to connect to a Remote Process Group Input Port. If the property is not configured, then give out the name of host running the NiFi instance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)