[
https://issues.apache.org/jira/browse/NIFI-5710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16668067#comment-16668067
]
Randy Bovay commented on NIFI-5710:
-----------------------------------
I just noticed this issue, and have a question / concern around the third
bullet point.
" - 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."
We actually leverage this UUID value to be able to trace a flowfile throughout
the system. Does this imply that we will no longer be able to do that?
> 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)
