Superset doesn't see the database even though it is created and available to query

[andheroe]

I use this SQLAlchemy URL to connect Superset to Embucket: snowflake://embucket:XXXXXXXXXX@test/data_platform_db?host=embucket&port=3000&protocol=http&schema=data_platform_schema&warehouse=data_platform_db (password is hidden by XXX...) It clearly sets the database as data_platform_db. This database is created with an s3 volume. I can even query it in Superset using the full name to the table data_platform_db.data_platform_schema.test_statistics. Here is example of this: https://github.com/user-attachments/assets/8791988d-2ae2-458b-acb4-ab28797b4ae6 But as you can see from the recording, schema is not show in Superset interface. It's like it doesn't exist.

In Snowflake I haven't seen such behavior. I can use the short name of the table, because I can set the schema in Superset UI. https://github.com/user-attachments/assets/5837af3e-05c2-452e-94f1-b81143ac953e For Snowflake connection I used an SQLAlchemy URL so it matches the format of URL I use for Embucket: snowflake://embucket:XXXXXXXXXX@test/data_platform_db?host=embucket&port=3000&protocol=http&schema=data_platform_schema&warehouse=data_platform_db

We have looked into it with @osipovartem recently and it may be related to the fact, that with all requests to Embucket we pass context, and in this case it is the default one (embucket database) - the context does not use the data_platform_db database name which is correct in this case and is provided as part of URL.