Hello, can anyone help out with some Metabase lineage weirdness? In the screenshot below, the left-hand side is the actual table in DataHub that the BigQuery connector generated and manages. On the right is the lineage from the Metabase Dashboard. Instead of linking to the BQ table, it's creating it's own

web_profile_clicks

that doesn't actually exist anywhere.

01_transform

instead of

01_TRANSFORM

. Any ideas?

The Metabase connector uses using sqlineage package to build lineage from Cards Raw Queries. The problem is that the sqlineage return the table and scheme name in lowercase. The same problem occurs in BigQuery lineage extraction. There is a solution for that, but no one is attacking this issue for now.

Thanks Patrick. Is there an issue in GitHub that I can follow at least?

I already made a modification to try to solve this on the BigQuery side. As for Metabase, we did an implementation on our side with these improvements. Depending on my prioritization of tasks, I can implement these community connector improvements to help.

thanks, we will take a look at this

Thank you!

@dazzling-judge-80093 Replacing this line of code: https://github.com/datahub-project/datahub/blob/master/metadata-ingestion/src/datahub/ingestion/source/metabase.py#L470 for something like:

# It is necessary to use raw_name to enable uppercase
source = f"{table.schema.raw_name}.{table.raw_name}".split(".")
source_schema, source_table = source[-2], source[-1]

can solve the problem.

Any plans for getting this fixed in a later release? Would love to click on a BigQuery table and see which Metabase dashboards are using that table