[
https://issues.apache.org/jira/browse/NIFI-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15742366#comment-15742366
]
ASF GitHub Bot commented on NIFI-2585:
--------------------------------------
GitHub user bbende opened a pull request:
https://github.com/apache/nifi/pull/1320
NIFI-2585 Add attributes to track s2s host and port
I left the three commits to show the history of how this evolved. We can
squash my two commits when merging, but I wanted Randy to get credit for
starting the work on this ticket.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bbende/nifi NIFI-2585
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1320.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1320
----
commit c6f0621f985b6deddadc616307f192c1ddf1060d
Author: Randy Gelhausen <[email protected]>
Date: 2016-12-07T07:18:09Z
NIFI-2585: Add attributes to track where a flow file came from when
receiving over site-to-site
commit 841c4c80e42f09e7dc96552c661dde5a81ab7c08
Author: Bryan Bende <[email protected]>
Date: 2016-12-08T20:17:06Z
NIFI-2585 Moving attributes into loop in AbstractFlowFileServerProtocol,
and also updating StandardRemoteGroupPort to apply the same attributes when
doing a pull-based site-to-site.
commit 0e3a29984d1abf94ba86d98fbe283e9671de1671
Author: Bryan Bende <[email protected]>
Date: 2016-12-12T14:19:22Z
NIFI-2585 Adding checks in case host and port are not known
----
> 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)
