Joseph Witt updated NIFI-2585:
    Fix Version/s:     (was: 1.1.0)

> 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
>            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

Reply via email to