*Hi guys We started using Tableau ingestion and ha...
# integrate-tableau-datahub
l
*Hi guys We started using Tableau ingestion and have question. Version of server and client 0.10.0 I set ingest_tables_external=True and see what I expected Dashboard -> Chart -> Embedded DS -> Published DS -> Vertica tables each vertica table looks good, with the correct urn like urnlidataset:(urnlidataPlatform:vertica,myDb.mySchema.myTable,PROD) , but when I open dataset details I expect to see this table in Datasrts under vertica platform. But see it in prod -> tableau -> Default -> mySchema I guess it because of this code in tableau.py
Copy code
table_path = None
            if project and datasource_name:
                table_path = (
                    f"{project.replace('/', REPLACE_SLASH_CHAR)}/{datasource_name}"
                )
is it possible to change this behaviour somehow? I want to ingest vertica source as usual and then ingest Tableau and make links between ingested vertica tables and Tableau charts
a
@dazzling-judge-80093 may be able to help here!
h
Hey @lively-jackal-83760! this can be easily achieved by updating the tableau codebase not to emit custom browse paths for external tables, however that needs a code change I was wondering why do you need to enable
ingest_tables_external
if you are already planning to ingest vertica tables from vertica ingestion source. If you can disable
ingest_tables_external
, you'll be able to see vertica dataset at the desired browse path as generated/expected by ingesting vertica source alone.
l
@hundreds-photographer-13496 Hi Thanks for answer. Yeah, I found in tableay.py the place, where I can rewrite this rule. I don't try to ingest Vertica tables via Tableau receipt. I want to ingest Vetica by vertica receipt first and then run Tableau receipt. And at the end see how vertica tables linked to Tableau reports, especially when these Vertica tables have upstreams to another pipelines. And see some issues - Vertica receipt generate brosePath aspect like {env}/vertica/{schema}, but Tableau like {env}/tableau/{project}/{schema}. Also Tableau's vertica tables contain db name and look like db.schema.table but from Vertica we have only schema and table, because db name configured in receipt That's why at the end I have 2 different datasets in Datahub for the same Vertica table db.schema.table in /{env}/tableu/{project}/{schema} and schema.table in /{env}/vertica/{schema} I think we should fix it
h
got it. can you create a github issue mentioning the urn generated by tableau source for vertica dataset as well as urn generated by vertica source for same dataset ? If you can submit a PR to fix this issue, that'd be great.