[
https://issues.apache.org/jira/browse/NIFI-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577576#comment-14577576
]
Matt Gilman commented on NIFI-578:
----------------------------------
[~markap14] For some reason I thought this was an issue at the DtoFactory
level. Looks like the LineageNode interface contains a cluster node identifier.
In FlowFileNode this will always return null. In EventNode there is at least a
corresponding setter however it is never invoked. I think the UI gets the
cluster node identifier from the provenance event that's the starting point for
the lineage graph. I'd recommend removing the method entirely but its part of
nifi-api. It's also not clear where I can get the cluster node identifier so it
can be populated. Thoughts?
> FlowFileNode does not set clusterNodeIdentifier
> -----------------------------------------------
>
> Key: NIFI-578
> URL: https://issues.apache.org/jira/browse/NIFI-578
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.0.2
> Reporter: Mark Latimer
> Assignee: Matt Gilman
> Priority: Minor
> Fix For: 0.2.0
>
>
> FlowFileNode class has a place to store the clusterNodeIdentifier and
> getClusterNodeIdentifier but the value for this is never set.
> The method is called in dtoFactory on types implementing LineageNode.
> Presumably some places expecting a value for the cluster node id are instead
> blank.
> It is not obvious to me what the cluster node id should be or where to get it
> from.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
