[
https://issues.apache.org/jira/browse/NIFI-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16294418#comment-16294418
]
ASF GitHub Bot commented on NIFI-3709:
--------------------------------------
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/2335
@markap14 I found that ReportLineageToAtlas does get UNKNOWN provenance
events when it queries lineage by
`ProvenanceRepository.submitLineageComputation(final long eventId, final
NiFiUser user)`. It uses the event hierarchies returned by that method, but to
analyze each event detail fully, it also calls
`ProvenanceEventRepository.getEvent(final long id)` which does not require
user. That's why the reporting task worked even in a secured NiFi cluster.
I now understand why NiFi framework has two interfaces for provenance
events, i.e. ProvenanceRepository and ProvenanceEventRepository.
`ProvenanceRepository` provides methods to be called in a context with a user
who made the request. `ProvenanceEventRepository` is used outside of a user
request, intended for Reporting Tasks, etc.
Is my understanding correct? If so, the approach of this PR looks good now?
Thanks!
> Export NiFi flow dataset lineage to Apache Atlas
> ------------------------------------------------
>
> Key: NIFI-3709
> URL: https://issues.apache.org/jira/browse/NIFI-3709
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
>
> While Apache NiFi has provenance and event level lineage support within its
> data flow, Apache Atlas also does manage lineage between dataset and process
> those interacting with such data.
> It would be beneficial for users who use both NiFi and Atlas and if they can
> see end-to-end data lineage on Atlas lineage graph, as some type of dataset
> are processed by both NiFi and technologies around Atlas such as Storm,
> Falcon or Sqoop. For example, Kafka topics and Hive tables.
> In order to make this integration happen, I propose a NiFi reporting task
> that analyzes NiFi flow then creates DataSet and Process entities in Atlas.
> The challenge is how to design NiFi flow dataset level lineage within Atlas
> lineage graph.
> If we just add a single NiFi process and connect every DataSet from/to it, it
> would be too ambiguous since it won't be clear which part of a NiFi flow
> actually interact with certain dataset.
> But if we put every NiFi processor as independent process in Atlas, it would
> be too granular, too. Also, we already have detailed event level lineage in
> NiFi, we wouldn't need the same level in Atlas.
> If we can group certain processors in a NiFI flow as a process in Atlas, it
> would be a nice granularity.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
