Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 33691200D0C for ; Wed, 6 Sep 2017 02:16:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 31DE01609E2; Wed, 6 Sep 2017 00:16:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 804971609C5 for ; Wed, 6 Sep 2017 02:16:06 +0200 (CEST) Received: (qmail 30109 invoked by uid 500); 6 Sep 2017 00:16:04 -0000 Mailing-List: contact issues-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.apache.org Delivered-To: mailing list issues@nifi.apache.org Received: (qmail 30100 invoked by uid 99); 6 Sep 2017 00:16:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Sep 2017 00:16:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 5D9B0C207B for ; Wed, 6 Sep 2017 00:16:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.001 X-Spam-Level: X-Spam-Status: No, score=-100.001 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id nFRDOf67Q90t for ; Wed, 6 Sep 2017 00:16:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id ECF7D61034 for ; Wed, 6 Sep 2017 00:16:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 32E6AE0DAF for ; Wed, 6 Sep 2017 00:16:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 7C6AB2415B for ; Wed, 6 Sep 2017 00:16:00 +0000 (UTC) Date: Wed, 6 Sep 2017 00:16:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@nifi.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (NIFI-3709) Export NiFi flow dataset lineage to Apache Atlas MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 06 Sep 2017 00:16:07 -0000 [ https://issues.apache.org/jira/browse/NIFI-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16154615#comment-16154615 ] ASF GitHub Bot commented on NIFI-3709: -------------------------------------- Github user ijokarumawak closed the pull request at: https://github.com/apache/nifi/pull/1676 > 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)