You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Koji Kawamura (JIRA)" <ji...@apache.org> on 2018/03/14 06:34:00 UTC
[jira] [Updated] (NIFI-4971) ReportLineageToAtlas 'complete path'
strategy can miss one-time lineages
[ https://issues.apache.org/jira/browse/NIFI-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Koji Kawamura updated NIFI-4971:
--------------------------------
Description:
For the simplest example, with GenerateFlowFile (GFF) -> PutFlowFile (PFF), where GFF generates FlowFiles with unique ids, and PFF creates local files, GFF ran 2 times, then following provenance events will be generated:
# GFF CREATE FF1
# PFF SEND file1
# PFF DROP FF1
# GFF CREATE FF2
# PFF SEND file2
# PFF DROP FF2
From above provenance events, following entities and lineages should be created in Atlas, labels in brackets are Atlas type names:
{code}
GenerateFlowFile (nifi_data)
-> GFF, PFF (nifi_flow_path) -> file1 (fs_path)
-> GFF, PFF (nifi_flow_path) -> file2 (fs_path)
{code}
Entities shown in above graph are created. However, those 'nifi_flow_path' entities do not have inputs/outputs referencing 'nifi_data' or 'fs_path', and lineage can not be seen in Atlas UI.
This issue was discovered by [~nayakmahesh616]
was:
For the simplest example, with GenerateFlowFile (GFF) -> PutFlowFile (PFF), where GFF generates FlowFiles with unique ids, and PFF creates local files, GFF ran 2 times, then following provenance events will be generated:
# GFF CREATE FF1
# PFF SEND file1
# PFF DROP FF1
# GFF CREATE FF2
# PFF SEND file2
# PFF DROP FF2
From above provenance events, following entities and lineages should be created in Atlas, labels in brackets are Atlas type names:
{code}
GenerateFlowFile (nifi_data)
-> GFF, PFF (nifi_flow_path) -> file1 (fs_path)
-> GFF, PFF (nifi_flow_path) -> file2 (fs_path)
{code}
Entities shown in above graph are created. However, those 'nifi_flow_path' entities do not have inputs/outputs referencing 'nifi_data' or 'fs_path', and lineage can not be seen in Atlas UI.
> ReportLineageToAtlas 'complete path' strategy can miss one-time lineages
> ------------------------------------------------------------------------
>
> Key: NIFI-4971
> URL: https://issues.apache.org/jira/browse/NIFI-4971
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.5.0
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
> Priority: Major
>
> For the simplest example, with GenerateFlowFile (GFF) -> PutFlowFile (PFF), where GFF generates FlowFiles with unique ids, and PFF creates local files, GFF ran 2 times, then following provenance events will be generated:
> # GFF CREATE FF1
> # PFF SEND file1
> # PFF DROP FF1
> # GFF CREATE FF2
> # PFF SEND file2
> # PFF DROP FF2
> From above provenance events, following entities and lineages should be created in Atlas, labels in brackets are Atlas type names:
> {code}
> GenerateFlowFile (nifi_data)
> -> GFF, PFF (nifi_flow_path) -> file1 (fs_path)
> -> GFF, PFF (nifi_flow_path) -> file2 (fs_path)
> {code}
> Entities shown in above graph are created. However, those 'nifi_flow_path' entities do not have inputs/outputs referencing 'nifi_data' or 'fs_path', and lineage can not be seen in Atlas UI.
> This issue was discovered by [~nayakmahesh616]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)