[ 
https://issues.apache.org/jira/browse/NIFI-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14703415#comment-14703415
 ] 

ASF subversion and git services commented on NIFI-868:
------------------------------------------------------

Commit 8f98f8093868e0ed2fb1dfbe3947f1afc1bdd10b in nifi's branch 
refs/heads/master from [~pukkaone]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=8f98f80 ]

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
>            Assignee: Joseph Witt
>             Fix For: 0.3.0
>
>
> 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)

Reply via email to