[
https://issues.apache.org/jira/browse/MINIFI-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15559226#comment-15559226
]
ASF GitHub Bot commented on MINIFI-119:
---
GitHub user randerzander opened a pull request:
https://github.com/apache/nifi-minifi-cpp/pull/19
MINIFI-119 add source.hostname to all flowfiles
[MINIFI-119](https://issues.apache.org/jira/browse/MINIFI-119)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/randerzander/nifi-minifi-cpp master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi-minifi-cpp/pull/19.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 #19
commit c87aa033355198934a772d68953f6817b7456c8b
Author: Randy Gelhausen
Date: 2016-10-09T04:07:42Z
MINIFI-119 add source.hostname to all flowfiles
> Append source.hostname attribute to FlowFiles sent via Site2Site
>
>
> Key: MINIFI-119
> URL: https://issues.apache.org/jira/browse/MINIFI-119
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: C++, Core Framework
>Reporter: Randy Gelhausen
>
> NiFi data consumers commonly need to know the original source (hostname) of
> flowfiles.
> NiFi collectors may create a unique input port per Site2Site client, but this
> in unmanageable with more than a trivial number of clients.
> Clients can manually inject source metadata as part of their flow
> definitions, but this is a burden that can be automated given that hostname
> is standard metadata. The Site2Site protocol implementation should
> automatically inject local hostname into FlowFiles.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)