You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by pukkaone <gi...@git.apache.org> on 2015/08/19 06:38:36 UTC

[GitHub] nifi pull request: NIFI-868 Configure advertised host name of Remo...

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.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: NIFI-868 Configure advertised host name of Remo...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/nifi/pull/74


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---