Hello! Not sure if the right channel to ask. I ingested information from Tableau and Athena on my datahub instance. Datahub correctly picks up that a published datasource on tableau is connected to an Athena table. The problem is that, the athena ingestor also picks up the same table, however Datahub does not recognize that they are both the same object. So basically what I have is, two entities that represent the same table but are considered separate objects. • The table that is picked up from the Tableau ingestor is called

awsdatacatalog.test-tableau-datasets.test_datasets

and has zero schema information, but is upstream of various tablueau datasources and charts. • The table picked up by the Athena ingestor is named only

test_datasets

and has schema information and is downstream of the correct Glue table. How could I tell Datahub that they are both the same table and that he should join the metadata from both entities? Thank you 🙂 Datahub version: acryl-datahub, version 0.8.36

Hi @fresh-napkin-5247 can you share urn for both the tables ?

• urnlidataset:(urnlidataPlatform:athena,awsdatacatalog.test-tableau-datasets.test_datasets,PROD) • urnlidataset:(urnlidataPlatform:athena,test-tableau-datasets.test_datasets,PROD) @hundreds-photographer-13496

Interesting. @hundreds-photographer-13496 Any chance this is data-platform-instance related? Or is tableau giving some name to this group of assets (awsdatacatalog)

I think its second case.

I'm wondering if we need to cut this out somehow - is there any way in tableau to detect?

actually this would be tableau connectionType specific. For athena, need to cut out the database part for correct urn. Got link for Common Tableau + Amazon Athena Errors from tableau blog mentioning this awsdatacatalog. I can raise a PR to handle this for athena.

Hello. Could you link me to the PR please?

Thank you!

@fresh-napkin-5247 just for information, which tableau version are you using ?

Thanks for the report, David. And the quick action Mayuri!

@hundreds-photographer-13496 I might need to get back to you on this tomorrow morning