[
https://issues.apache.org/jira/browse/NIFI-5710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16668744#comment-16668744
]
Mark Payne commented on NIFI-5710:
----------------------------------
[~randy_b] If a FlowFile is transferred from Node A to Node B, then Node B will
assign a new UUID to the FlowFile. This is because Node A has finished its work
with the FlowFile and it is a new FlowFile on Node B with the same content and
attributes. The correlation can be made via the Provenance RECEIVE event (via
the Source System UUID field).
I'm not sure if I am fully answering your question here. I think I would need
to understand more about how you are using the UUID to trace a flowfile through
the system.
> Minor bugs introduced into 1.8.0
> --------------------------------
>
> Key: NIFI-5710
> URL: https://issues.apache.org/jira/browse/NIFI-5710
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.8.0
>
>
> I've encountered a couple of minor bugs in 1.8.0. Since they can be fixed
> before 1.8.0 is released and they are quite minor, I am creating a single
> Jira to encompass them all:
> * When obtaining processor diagnostics, the garbage collection info is
> sorted in the wrong order in a cluster and not sorted at all in standalone
> mode.
> * When obtaining processor diagnostics, a NullPointerException is thrown if
> the Processor allows the user to reference a controller service but no
> controller service is currently configured.
> * When load balancing a connection, the same UUID is assigned to the
> flowfile on the receiving side. It should be a unique UUID on the receiving
> side and just reference the UUID of the sending side in the Source System
> UUID field of the RECEIVE provenance event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
