You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "shenyubin1990 (via GitHub)" <gi...@apache.org> on 2023/06/13 05:55:15 UTC

[GitHub] [superset] shenyubin1990 commented on issue #22420: Superset failed to get Databricks tables

shenyubin1990 commented on issue #22420:
URL: https://github.com/apache/superset/issues/22420#issuecomment-1588591540

   Hi Nagaraj,
   
   I found the same issue like you described. I think you can try to run select current_catalog() to see if the catalog is the one you want to use. In my case, it will point to the first catalog in your sql warehouse even if you assigned the different database name. Unfortunately I haven't found a way to fix it, but I think that is a good start to dive deep. 


-- 
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-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org