[ https://issues.apache.org/jira/browse/NIFI-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449940#comment-16449940 ]
ASF GitHub Bot commented on NIFI-4971: -------------------------------------- Github user MikeThomsen commented on the issue: https://github.com/apache/nifi/pull/2542 I set everything up and set it to do `complete path.` This is what I got in Atlas: <img width="1292" alt="screen shot 2018-04-24 at 10 17 16 am" src="https://user-images.githubusercontent.com/108184/39193186-f45d018c-47a8-11e8-9774-5c958d81bcb3.png"> <img width="1296" alt="screen shot 2018-04-24 at 10 18 03 am" src="https://user-images.githubusercontent.com/108184/39193187-f46e1b0c-47a8-11e8-9601-2ae647d58353.png"> > 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 GetFlowFIle (GFF) -> PutFlowFile (PFF), where > GFF gets files and PFF saves those files into a different directory, then > following provenance events will be generated: > # GFF RECEIVE file1 > # PFF SEND file2 > From above provenance events, following entities and lineages should be > created in Atlas, labels in brackets are Atlas type names: > {code} > file1 (fs_path) -> GFF, PFF (nifi_flow_path) -> file2 (fs_path) > {code} > Entities shown in above graph are created. However, the 'nifi_flow_path' > entity do not have inputs/outputs referencing 'fs_path', so 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)