ziggekatten commented on issue #32429: URL: https://github.com/apache/superset/issues/32429#issuecomment-2903768046
> > We have the same issue with trino. The workaround does not work for us as we have some joins between catalog. This is a pain, as we would like to change some labels an metrics. > > We also needed to do joins between catalogs and change some of the data structure. We ended up using dbt to generate these view tables with all the joins (dbt connects to trino and uses its catalogs) and we stored these view in a hive instance which is also a catalog in trino (we started with a memory catalog for testing, but that only lives in memory and we of course need a permanent catalog). > > So dbt connects to trino and uses its catalogs to generate views which are stored in the hive instance via trino as well. Then in superset we connect to trino.hive which has all the views with all the joins ready. The good thing about this is that we can use these views outside of superset and they are managed through different sql files (that dbt executes). There is a performance hit but we are currently working on that. > > If someone has a better approach don't hesitate to comment. This is the best I could come up with. Ohhh....good point. We use dbt and Nessie as a catalog. Time to experiment! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
