[jira] [Resolved] (NIFI-10064) Provenance shown wrong lineage with multi-clone event

["Pierre Villard (Jira)" <ji...@apache.org>]

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

Pierre Villard resolved NIFI-10064.
-----------------------------------
    Resolution: Feedback Received

Apache NiFi 1.x is no longer maintained and no new release is planned on the 1.x release line. Marking as resolved as part of a cleanup operation. Please open a new one with an updated description if this is still relevant for NiFi 2.x.

> Provenance shown wrong lineage with multi-clone event
> -----------------------------------------------------
>
>                 Key: NIFI-10064
>                 URL: https://issues.apache.org/jira/browse/NIFI-10064
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.16.0, 1.16.1, 1.16.2
>            Reporter: super dachuan
>            Priority: Major
>         Attachments: image-20220530142139606.png
>
>
> When I upgraded my NiFi cluster from 1.15.3 to 1.16.0, provenance with lineage shown wrong graph. For example, DROP event should be the last node, but now is the parent of another node with different clone branch.
> After I changed the implemention of provenance, this problem persisted. Maybe the provenance is something wrong with CLONE events when it's generated.
> Also existing in the minor upgraded version 1.16.1 and 1.16.2.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)