[
https://issues.apache.org/jira/browse/NIFI-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770340#comment-15770340
]
ASF GitHub Bot commented on NIFI-2585:
--------------------------------------
Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/1342
I think the issue was that I had left nifi.remote.input.host blank on both
instances. So in the push model it was getting the ip address of the incoming
connection which was my laptop's internal IP that doesn't resolve to a
hostname, and in the pull model it was receiving the hostname of the peer from
the peer itself (line 228 of SocketClientProtocol) which happened to be
hostname of my laptop.
When I set nifi.remote.input.host to localhost for both of the instances,
then I always get localhost in the attributes which is good.
I'm a +1, will go ahead and merge. Thanks!
> Add attributes to track where a flow file came from when receiving over
> site-to-site
> ------------------------------------------------------------------------------------
>
> Key: NIFI-2585
> URL: https://issues.apache.org/jira/browse/NIFI-2585
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Bryan Bende
> Assignee: Randy Gelhausen
> Priority: Minor
>
> With MiNiFi starting be used to send data to a central NiFi, it would be
> helpful if information about the sending host and port was added to each flow
> file received over site-to-site. Currently this information is available and
> used to generate the transit URI in the RECEIVE event, but this information
> isn't available to downstream processors that might want to make routing
> decisions.
> For reference:
> https://github.com/apache/nifi/blob/e23b2356172e128086585fe2c425523c3628d0e7/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-site-to-site/src/main/java/org/apache/nifi/remote/protocol/AbstractFlowFileServerProtocol.java#L452
> A possible approach might be to add two attributes to each flow file,
> something like "remote.host" and "remote.address" where remote.host has only
> the sending hostname, and remote.address has the sending host and port.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
