Hi, I am not sure if this has already been asked f...
# feature-requests
s
Hi, I am not sure if this has already been asked for yet. Has there been any consideration of how the lineage data may be used to trace impact to owners of the datasets? For example, instead of seeing all of the impacted tables can we also get a view of impacted owners? It would be helpful in understanding who would need to be contacted in the event of a change or quality issue
m
I think if you export in the csv format, you can see the owners
s
Wondering if this is something that could be automated in the tool to make it easier for stakeholders to use
r
Could we see the owners in the diagram itself? The diagram is displaying now lineage type of predicates, but could it allow to display other type of predicates? It can get messy, so we would need filters or other functionality to allow users curate the diagram.
b
@little-megabyte-1074 to help track the feature request. We are actively considering options for better filtering the lineage graph. cc @green-football-43791 @bulky-soccer-26729
@steep-pizza-43061 The easiest way to do this in systematic way is to download to CSV from the "impact analysis" tab. You can also see a list of owners in the ride side filter panel 🙂
How would you like to see this information? As Franco mentioned, would putting this information directly inside of the lineage graph view be useful for you?
s
Actually I think that perhaps the filters for owners in the data dependencies may be enough to answer the questions that our team need if we can also do this when the column lineage is in place mapping. What I hadn’t spotted is that the degree of dependencies are actually in the list.
it possibly just needs the owners to be made more prominent (of moved out of the filter) in that list and for the degree of dependencies (e.g. 1st, 2nd, 3rd) just to be a bit clearer to make it easier for the more casual user
m
@steep-pizza-43061 anything can be done in the front end should be able to achieve through api. You can embed your filtering logic after the api call.