[
https://issues.apache.org/jira/browse/NIFI-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474982#comment-16474982
]
ASF GitHub Bot commented on NIFI-4971:
--------------------------------------
Github user MikeThomsen commented on the issue:
https://github.com/apache/nifi/pull/2542
@ijokarumawak I went back and looked at the Jira ticket again, and my
interpretation is that what I saw in the screenshots above (with the graph)
matches your description of the behavior you wanted to implement.
> 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)
