[jira] [Commented] (NIFI-3709) Export NiFi flow dataset lineage to Apache Atlas

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971333#comment-15971333 ] 

ASF GitHub Bot commented on NIFI-3709:
--------------------------------------

GitHub user ijokarumawak opened a pull request:

    https://github.com/apache/nifi/pull/1676

    NIFI-3709: NiFi flow lineage to Apache Atlas.

    Adding AtlasNiFiFlowLineage reporting task to create NiFi lineage in
    Atlas. See the additionalDetails.html for details.
    
    Thank you for submitting a contribution to Apache NiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [x] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [x] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    - [x] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
    - [x] Have you written or updated unit tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
    - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
    - [x] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [x] Have you ensured that format looks appropriate for the output in which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ijokarumawak/nifi nifi-3709

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/1676.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1676
    
----
commit 70573ba42b282cc92fbbab5d631dd0ed21ab9a00
Author: Koji Kawamura <ij...@apache.org>
Date:   2017-03-27T23:01:02Z

    NIFI-3709: NiFi flow lineage to Apache Atlas.
    
    Adding AtlasNiFiFlowLineage reporting task to create NiFi lineage in
    Atlas. See the additionalDetails.html for details.

----


> 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.3.15#6346)