Uploaded image for project: 'Apache NiFi'
  1. Apache NiFi
  2. NIFI-3709

Export NiFi flow dataset lineage to Apache Atlas

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.5.0
    • Extensions
    • None

    Description

      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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            ijokarumawak Koji Kawamura
            ijokarumawak Koji Kawamura
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 20m
                20m

                Slack

                  Issue deployment