Surface materialized views in view names #1459
Labels
🕹 aspect: interface
Concerns end-users' experience with the software
🧰 goal: internal improvement
Improvement that benefits maintainers, not users
🟩 priority: low
Low priority and doesn't need to be rushed
🧱 stack: catalog
Related to the catalog and Airflow DAGs
💾 tech: postgres
Involves PostgreSQL
🐍 tech: python
Involves Python
Projects
Description
Right now we have we have a mix of views & materialized views in the database. For instance,
audio_view
andaudioset_view
- the former is actually a materialized view whereas the latter is a standard view. The syntax for operating with these tables can be different (e.g.DROP MATERIALIZED VIEW
vsDROP VIEW
).It might be useful to reflect which views are actually materialized by incorporating it in their name. We could use
matview
instead of view for the suffix. Here are the current tables:This would mean we'd update the following:
audio_view
->audio_matview
image_view
->image_matview
I'm excluding the popularity constants matviews because they do not have any suffix, but perhaps we should add suffixes there as well.
Note that this will also necessarily require changes in the ingestion server code for which tables to reference.
Implementation
The text was updated successfully, but these errors were encountered: