Hey there’s a bug with `looker` ingestion source -...
# ingestion
b
Hey there’s a bug with
looker
ingestion source - I’ve made a small PR to resolve the issue - https://github.com/linkedin/datahub/pull/3158
m
@bumpy-activity-74405: thanks for the PR. It seems simple enough, but I'm curious. What is the use-case for ingesting deleted dashboards? Do you expect to search for them in DataHub? Would it be confusing to find a deleted dashboard?
b
I don’t want to see or be able to find deleted dashboards. Running ingestion daily so dashboards deleted after last run would get hidden by the next one. The way the code was written (adding a status aspect) I thought that was the intention, the problem is that deleted dashboards never got ingested.
m
that makes sense! Thanks for the explanation 🙂
@high-hospital-85984 makes some good points in his review... this seems to fall into the general category of -> detecting deleted entries cheaply and soft-deleting them on the next ingest. This is a common problem across our sources and needs a common solution IMO.
b
Hey @high-hospital-85984, @mammoth-bear-12532 I’ve made the ingestion of deleted dashbaords optional - https://github.com/linkedin/datahub/pull/3158/files. I hope that works for you.
h
Works for me. We anyway basically hardcode the dashboards we're interested (as regex and numbers aren't the best combination 😅 ).
b
Out of curiosity - what do you do if a dashboard gets deleted?
h
use your flag.
or soft-delete manually