liurenjie1024 commented on issue #246:
URL: https://github.com/apache/iceberg-rust/issues/246#issuecomment-1996758139
> > It's kind of weird to me to have both of them. Is there any concrete use
case?
>
>
>
> Database like databend supports loading iceberg table from both catalog or
paths of a storage services.
>
>
>
> For example:
>
>
>
> ```sql
>
> CREATE TABLE <table_name>
>
> ENGINE = Iceberg
>
> LOCATION = 's3://<path_to_table>'
>
> CONNECTION_NAME = '<connection_name>'
>
> ```
>
>
>
> If we provides `Table` and `StaticTable`, users will need to wrap them
again like the following.
>
>
>
> ```rust
>
> enum IcebergTable {
>
> Table(iceberg::Table), // build from catalog
>
> StaticTable(iceberg::StaticTable) // build from a path of table metadata
>
> }
>
> ```
Make sense. Will following code work for you?
```
struct Table <const N: bool>{}
```
--
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: issues-unsubscr...@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For additional commands, e-mail: issues-h...@iceberg.apache.org
