- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2025 11:32 PM - edited 09-14-2025 11:35 PM
Goal: event-driven without implementing job triggereed on file arrival
I see hope to incrementally update materialized views which have external tables as their sources.
This is quite a game changer if it works for various data formats.
(since MV started supporting trigger on update recently)
Incremental refresh for materialized views | Databricks on AWS
it mentioned that materialized view support "external table backed by delta lake"
- Delta tables, including Unity Catalog managed tables and external tables backed by Delta Lake.
does it mean external source data required to be in delta format? or parquet format data source can be external table backed by delta lake if it is declared as an external table properly?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2025 12:13 AM - edited 09-15-2025 12:20 AM
Hi @tana_sakakimiya ,
Yes, only external tables that are in delta format are supported. Databricks supports other table formats, but to be able to use this particular feature, your table needs to be in Delta format.
But if you have parquet files it's really easy to convert them to delta format, so that shouldn't be an issue here.