[
https://issues.apache.org/jira/browse/NIFI-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564443#comment-17564443
]
Mark Payne commented on NIFI-10203:
-----------------------------------
For clarification about what this affects:
I was able to confirm that while the same UUID gets assigned to the clones, and
this does cause problems for the data lineage, the processing of all clones
appears to behave as expected otherwise.
So this will cause confusion with data provenance and will make the logs
confusing.
However, it does not result in the FlowFiles getting mixed attributes
otherwise, or referencing the wrong content, or prematurely removing content,
or anything like that.
Additionally, the FlowFile Repository refers to the FlowFiles via the one-up
"ID" field, not the UUID field, so we don't run into additional issues after a
restart.
Will mark this as a Blocker priority, since it wouldn't make sense to release
without getting this fixed first.
> Multi-connection relationship clone flowfile with same uuid
> -----------------------------------------------------------
>
> Key: NIFI-10203
> URL: https://issues.apache.org/jira/browse/NIFI-10203
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.16.0, 1.16.1, 1.16.2, 1.16.3
> Reporter: super dachuan
> Assignee: Mark Payne
> Priority: Blocker
> Fix For: 1.17.0
>
> Attachments: Snipaste_2022-07-08_18-23-12.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> A relationship could be generated many connections as we need , likes the
> picture. Framework clone the orginal flowfile and transfer to all connection.
> However, these flowfiles have same uuid, we expected every flowfile has
> unique uuid like the older versions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
