I see what you're saying about the reuse. Lineage clutter is definitely the main issue we're facing. Regardless, we've tried modifying the queries responsible for displaying the lineage graph to no avail. Are you saying that feature would need to be developed? Are there any features in place that could help with this?
... View more
I am struggling to find a solution for this issue. My team is creating spark/presto plugins to create new relationship/lineage metadata in Atlas. After awhile, the lineage becomes very cluttered with deleted entities, which remain in the UI. We therefore want to reuse entities. I'll give you an example: User creates hive_table named fully.qualified.name User updates table User deletes table User creates hive_table named fully.qualified.name In the above scenario, Atlas is aware of two entities with the qualifiedName 'fully.qualified.name' with one in DELETED status and one in ACTIVE status. I want the second creation to simply reuse the DELETED entity and update its status to ACTIVE along with any other attribute updates. The audit will now show its full lifecycle, including deletes. We can find the deleted entity with a dsl search and run a POST with that entity's guid, but nothing happens. I can't find any way to update properties as opposed to attributes. Is this possible? Are we going about this the wrong way? After finding no info regarding what seems to be a simple operation, I'm inclined to believe I'm doing something wrong. Thanks for any help!
... View more