Learn how to use the Hosted Iceberg Catalog in RisingWave. This guide shows you how to create and manage Iceberg tables without the need to configure or maintain an external catalog service like AWS Glue or a JDBC database.
ENGINE = iceberg
clause is stored within two system views in RisingWave: iceberg_tables
and iceberg_namespace_properties
.hosted_catalog
parameter to true
.
<storage_path>
and <object_storage_parameters>
depend on your chosen storage backend (S3, GCS, or Azure Blob). See the object storage configuration for specific parameter details.
Field | Description |
---|---|
hosted_catalog | Required. Set to true to enable the Hosted Iceberg Catalog for this connection. This instructs RisingWave to manage the catalog metadata internally. |
ENGINE = iceberg
. RisingWave will use the hosted catalog to manage its metadata.
Iceberg | RisingWave |
---|---|
catalog name | database name |
namespace | schema |
table | table |
t_hosted_catalog
table created in the example above. In this Spark SQL command, assume the table was created in the RisingWave database named dev
and schema public
.
catalog.namespace.table
):
iceberg_tables
and iceberg_namespace_properties
directly in RisingWave to see the catalog’s metadata. The catalog exposed by RisingWave is read-only.