[
https://issues.apache.org/jira/browse/NIFI-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15768359#comment-15768359
]
ASF GitHub Bot commented on NIFI-2585:
--------------------------------------
Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/1342
Thanks @ijokarumawak !
I was testing this and I noticed that whenever I do a push model from
nifi-1 to nifi-2, the value of s2s.hostname on the flow file in nifi-2 ends up
being the IP address of my laptop.
Whenever I do a pull model, where nifi-2 pulls from nifi-1, the value of
s2s.hostname on the flow file in nifi-2 ends up being the hostname of my laptop.
I don't know if this is important or not, but I know you made some code
changes to try and resolve the hostname, so would you expect this behavior?
In my setup I haven't changed much configuration... I set the remote port
in nifi.properties of nifi-1, and the same thing in nifi-2, and also change web
port in nifi-2, everything else is using defaults.
> 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)
