[ https://issues.apache.org/jira/browse/NIFI-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764414#comment-15764414 ]
ASF GitHub Bot commented on NIFI-2585: -------------------------------------- Github user bbende commented on the issue: https://github.com/apache/nifi/pull/1342 @ijokarumawak thanks for digging in to this! I closed the other PR. Everything you described makes sense... I'm on the fence about the attribute names... lets say we have MiNiFi -> s2s -> NiFi, the s2s.address is always going to be the address of MiNiFi, but from the address we don't know if MiNiFi was the client (push to NiFi) vs the server (NiFi pull from MiNiFi). I was originally thinking of having a third attribute like s2s.direction which could have values of "push" or "pull" which then gives you context about the host and port. What do you think? > 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)