Hi, have a question regarding lineage. We are ingesting lineage (both table and column/finegrained) via python REST and we encounter an issue. Somehow the lineage were gone after a few seconds refreshing after ingesting even though it shows at first in UI.

Hi Henry, do you have any metadata tests or automation active in your instance? CC: @bulky-soccer-26729

hey! so is the second screenshot consistent every time you view this lineage now (even after multiple refreshes or coming back later?

Just managed to solve it yesterday, turns out you need to pass the full upstream table lineage for that table in the upstreams when creating lineage for fineGrained.

fieldLineages = UpstreamLineage(
        upstreams=upstreams, fineGrainedLineages=fineGrainedLineages
    )

Still not sure why it is behaving that way though as the lineage were pictured correctly at first in UI. And yes it is consistent when I did not put the complete table lineage for upstreams. I also checked the response for the graphql api call in the UI and the finegrainedLineage still exist but lineageRelationship is gone in the second screenshot, whereas both exist in the first screenshot.