Uploaded image for project: 'Atlas'
  1. Atlas
  2. ATLAS-4606

Improve Atlas Lineage API performance (fetch on-demand)

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.0.0, 2.3.0
    • atlas-core
    • None

    Description

      Atlas lineage for an entity returns all the entities connected in a single call, this is expensive if lineage is long and has multi-level. Lineage API response is large and UI fails to render the response. 

      Attachments

        Issue Links

          fixes

          Bug - A problem which impairs or prevents the functions of the product. ATLAS-4645 [Lineage Improvements] When inputRelationsLimit or outputRelationsLimit is 0, then it is replaced with the default value of node count

          • Major - Major loss of function.
          • Resolved
          relates to

          Bug - A problem which impairs or prevents the functions of the product. ATLAS-4644 [Lineage Improvements] When direction is 'INPUT' for a lineage which does not have inputs, the response does not contain guidEntityMap

          • Major - Major loss of function.
          • Resolved
          requires

          Improvement - An improvement or enhancement to an existing feature or task. ATLAS-4607 UI improvements to support Atlas Lineage fetch on-demand

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link Code Review

          Activity

            People

              radhikak Radhika Kundam
              radhikak Radhika Kundam
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: