Closed liurenjie1024 closed 1 year ago
The open api spec is here: https://github.com/apache/iceberg/blob/master/open-api/rest-catalog-open-api.yaml
We can use https://openapi-generator.tech/docs/installation#homebrew to generate rust code for it. But one thing to discuss is that whether we should keep the generated code in repo?
Personally I prefer to keep them in repo to simplify whole thing, how do you guys think?
cc @ZENOTME @Xuanwo
Personally I prefer to keep them in repo to simplify whole thing, how do you guys think?
I perfer to keep them so that our users don't need to generate again.
+1. Sounds reasonable for me.
Cool, let's keep them
Hi, Our team are experimenting Trino + Iceberg with Nessie Catalog (can be replaced with rest catalog), the query experience is good. The missing part is data ingestion, we want to use icelake
to ingest data to our lakehouse, the missing rest catalog support prevent us from doing so.
So what's the status about this?
BTW: icelake
is a great project.
We have plans to support this, due to the schedule, maybe one month later we will start to implement it.
Tracked in #172
The current implementation only supports filesystem catalog. In production, jdbc/hive metastore catalogs are widely used. To support them, we need to support rest catalog so that we don't need to interact with them directly.