dosubot[bot] commented on issue #34408: URL: https://github.com/apache/superset/issues/34408#issuecomment-3137360254
<!-- Greeting --> Hi @rmcdonough-look! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team. <!-- Answer --> You're correct—Superset relies on the SQLAlchemy dialect (pybigquery) to discover schema objects, so if pybigquery doesn't include "MATERIALIZED VIEW" in its discovery logic, materialized views won't appear in the schema dropdown by default. When patched, Superset displays them, but the frontend only distinguishes between "view" and "table" types: if the type is "view", it shows a generic view icon; otherwise, it shows a table icon. There is no dedicated handling or icon for materialized views in the UI, so they're currently indistinguishable from standard views in the dropdown, which can be misleading for BigQuery users who care about performance and cost differences ([source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/src/components/TableSelector/index.tsx)). To fully support materialized views, both pybigquery and Superset would need updates: pybigquery should return "MATERIALIZED VIEW" as a distinct type, and the Superset frontend should map this type to a unique icon or label. There are currently no official docs, issues, or recent PRs addressing this in Superset as of July 2025. If you need this feature now, you can patch pybigquery to include "MATERIALIZED VIEW" and, for a better UI experience, consider customizing the Superset frontend to recognize and display a distinct icon or label for this type. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/326b2608-7d8a-4aa5-acb9-110370cfede4?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/326b2608-7d8a-4aa5-acb9-110370cfede4?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/326b2608-7d8a-4aa5-acb9-110370cfede4?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/326b2608-7d8a-4aa5-acb9-110370cfede4?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/326b2608-7d8a-4aa5-acb9-110370cfede4?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/326b2608-7d8a-4aa5-acb9-110370cfede4?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/326b2608-7d8a-4aa5-acb9-110370cfede4?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu b) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/34408) -- 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
