[
https://issues.apache.org/jira/browse/NIFI-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823804#comment-16823804
]
ASF subversion and git services commented on NIFI-6220:
-------------------------------------------------------
Commit 055b3cac54e3e234c0ee07189b7b7b85e0582d58 in nifi's branch
refs/heads/master from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=055b3ca ]
NIFI-6220: If FlowFile is created by cloning a relationship, do not create an
ATTRIBUTES_MODIFIED provenance event for it.
NIFI-6220: Updated test name and fixed typo
This closes #3438.
Signed-off-by: Koji Kawamura <[email protected]>
> Cloning a FlowFile results in unnecessary ATTRIBUTES_MODIFIED provenance event
> ------------------------------------------------------------------------------
>
> Key: NIFI-6220
> URL: https://issues.apache.org/jira/browse/NIFI-6220
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.10.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> When a FlowFile is cloned by connecting a component's relationship to
> multiple outputs, a provenance CLONE event is created. However, it also
> currently is creating an ATTRIBUTES_MODIFIED event, showing that all
> attributes were modified.
> To replicate, create a GenerateFlowFile and connect its 'success'
> relationship to two different processors. Run the flow, then look at the
> lineage for one of the FlowFiles. it will show a FlowFile was CREATEd, then
> CLONEd. But if you expand the CLONE event, there will also be an
> ATTRIBUTES_MODIFIED event that shows all attributes having been added. This
> event should not exist.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
