rmcdonough-look opened a new issue, #34408:
URL: https://github.com/apache/superset/issues/34408
### Bug description
### Summary
Materialized views in BigQuery are not shown in Superset's schema dropdown
by default. When patched to include `"MATERIALIZED VIEW"` using values from
`INFORMATION_SCHEMA.TABLES`, Superset does display the view — but it uses a
**generic "view" icon**, even though the object is a **materialized view**, not
a standard view.
This can be misleading for users, especially when differentiating
performance/cost expectations in BigQuery.
### Steps to Reproduce
1. Create a materialized view in BigQuery (e.g., `CREATE MATERIALIZED VIEW
dev.mv_example AS ...`)
2. Use Superset with a BigQuery connection via SQLAlchemy URI:
`bigquery://my-project?location=us-central1`
3. In Superset, materialized views are:
- ❌ Not listed by default
- ✅ Can be shown if manually patched in `pybigquery` to include
`MATERIALIZED VIEW`
- ❌ But are shown with a **"view" icon**, not a dedicated or "table" icon
### Expected Behavior
- Superset should list materialized views by default in the schema browser
- Materialized views should have a **distinct icon** or at least not reuse
the "view" icon
- Superset should support adding them as datasets directly through the UI
dropdown
### Suggested Fix
In `pybigquery`:
- Ensure `_get_table_or_view_names()` includes `'MATERIALIZED VIEW'` based
on `INFORMATION_SCHEMA.TABLES.table_type`
- In Superset's UI or backend, use a different icon or label if `table_type
== 'MATERIALIZED VIEW'`
### Environment
- Superset version: 3.0.x
- pybigquery: latest
- Deployment: GCP Compute Engine VM using ADC (Application Default
Credentials)
### Screenshots/recordings
<img width="987" height="909" alt="Image"
src="https://github.com/user-attachments/assets/1e84bb0f-a522-4897-b6d3-c33e82b1628a";
/>
### Superset version
5.0.0
### Python version
Not applicable
### Node version
Not applicable
### Browser
Firefox
### Additional context
_No response_
### Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to
my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug
report.
- [x] I have checked Superset's logs for errors and if I found a relevant
Python stacktrace, I included it here as text in the "additional context"
section.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
