Good morning :sunrise_over_mountains: I'm having s...
# troubleshoot
b
Good morning 🌄 I'm having some difficulty with impact analysis. With DataHub quickstart on Docker I've ingested Snowflake, DBT and Looker. I can see table and column lineage in the lineage visualisation and list. But when I choose to export the lineage in a .csv file, (using Lineage > 3 dots > Download) I only get the headers, and no rows of data. There is lineage shown on the "lineage" tab at the time I do the export, this happens for all platforms, and the issue persists after a nuke-and-reingest. All platforms are ingested via CLI. DataHub CLI version 0.10.2.2 Python 3.10.11
🔍 1
📖 1
🐛 1
l
Hey there 👋 I'm The DataHub Community Support bot. I'm here to help make sure the community can best support you with your request. Let's double check a few things first: ✅ There's a lot of good information on our docs site: www.datahubproject.io/docs, Have you searched there for a solution? ✅ button ✅ It's not uncommon that someone has run into your exact problem before in the community. Have you searched Slack for similar issues? ✅ button Did you find a solution to your issue? Yes button No button
b
Things I've tried: • Nuking, updating acryl-datahub packages in my virtual environment, docker prune, quickstart with default ports. • Different platforms (Snowflake, Looker), different datasets, • Upstream vs downstream, etc • Changing date ranges • Filtering, not filtering • Using a login with an admin role Other csv exports (e.g of search) work fine.
I think I found it: It seems that
Degree of Dependencies
filter blocks records from being exported. If I swap to "advanced" filters and remove this filter criteria totally, then my exported csv contains records. (Edit: possible confounding factor; I switched my quickstart to use postgres instead of mysql. I don't think that's made a difference, but i haven't changed it back and re-ingested to be sure.)
a
Hi Sara, we’ll get this looked at- thanks for logging the bug 🙂 CC: @big-carpet-38439
a
Thank you! Looking into this
k
@astonishing-answer-96712 @big-carpet-38439 We have this issue in datahub version 0.10.5.5 as well, I see this ticket has been marked stale, Please suggest. This feature was working fine in 0.9.3 version