[
https://issues.apache.org/jira/browse/NIFI-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506052#comment-16506052
]
ASF GitHub Bot commented on NIFI-5155:
--------------------------------------
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/2773
I'm not exactly sure why the Bulletin itself has a `nodeAddress` field.
However, I can offer that the corresponding BulletinDTO contains a
`nodeAddress` to help differentiate between which node in the cluster is
reporting the message. This is populated when the responses are merged at the
cluster coordinator. In standalone mode, there is only a single instance so
this field does not need to be populated. This is also how component
`validationErrors` work.
> Bulletins do not include IP/hostname information
> ------------------------------------------------
>
> Key: NIFI-5155
> URL: https://issues.apache.org/jira/browse/NIFI-5155
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
>
> There is an API call on Bulletin for setNodeAddress(), which is meant to set
> the node on which a bulletin/error has occurred. The
> SiteToSiteBulletinReportingTask uses getNodeAddress() to add said field to
> the outgoing records (if available). However, the framework is not calling
> setNodeAddress() anywhere, which results in the field being missing from the
> outgoing records.
> NiFi should add the appropriate node address information to the outgoing
> bulletin information.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
