Xuanwo
All work have been done, let's close.
Forward @JanKaul's discussion here.
From @Xuanwo > Thank you for sharing! The relationship between `view` and `table` is quite interesting. At Databend, we consider a `view` as a special type of `table`, and our...
From @JanKaul > Converting from Table to TableLike is straightforward: > > ```rust > impl From for TableLike { > fn from(value: Table) -> Self { > TableLike::Table(value) > }...
Also invite @Fokko, @liurenjie1024，@ZENOTME to join this discussion.
> Can you think of an ideal design for databend that supports tables and views? Databend has a `TableMeta` that carries the `engine` used by this table: https://github.com/datafuselabs/databend/blob/main/src/meta/app/src/schema/table.rs#L217 ```rust pub...
I'm guessing the problem we met here is iceberg has different spec for `Table` and `View` which needs different handling?
From @liurenjie1024 > Hi, @JanKaul Good point for view. Except for view, I think there will be other entities like [materialized view](https://github.com/apache/iceberg/issues/6420). So the question is about name resolution: >...
> So for constructing `TableMeta` for views and tables, wouldn't you also need a `TableLike` to specify the correct `engine`? Oh, sorry for missing this part. We have those information...
> What if you use an external iceberg catalog? Do you still have that information? Great point! This information is essential. Thank you for the explanation. Now I got your...