[
https://issues.apache.org/jira/browse/NIFI-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15735481#comment-15735481
]
ASF GitHub Bot commented on NIFI-2585:
--------------------------------------
Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/1307
@randerzander I haven't been able to reproduce this yet. Running a simple
GetFile -> RPG on minifi-cpp to a regular NiFi with InputPort -> LogAttribute,
I am seeing the two attributes come through correctly.
I'm trying to look at the rest of the s2s code to see how a Peer instance
could be created and not get the correct host or port. Would you be able to add
the following code to the end of the Peer constructor?
https://github.com/apache/nifi/blob/master/nifi-commons/nifi-site-to-site-client/src/main/java/org/apache/nifi/remote/Peer.java#L51
```
if (this.host == null || this.port == -1) {
throw new IllegalStateException("Unable to get host or port
from peerUrl" + peerUrl);
}
```
My theory is that it somehow the parsing of the URI is considered
successful, but it didn't actually find a host or port, since the Javadocs of
uri.getPort() say it can return -1. Let me know if you can get that stacktrace
from that added code to see what the peerUrl is when this happens. 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)
