You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2019/04/16 18:54:00 UTC

[jira] [Updated] (NIFI-6220) Cloning a FlowFile results in unnecessary ATTRIBUTES_MODIFIED provenance event

     [ https://issues.apache.org/jira/browse/NIFI-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Payne updated NIFI-6220:
-----------------------------
    Fix Version/s: 1.10.0
           Status: Patch Available  (was: Open)

> 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: 10m
>  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)