Learn how to use the Iceberg table engine in RisingWave to store data natively in the Iceberg format.
CREATE CONNECTION
.
The following examples show how to create an Iceberg connection using different catalog types.
CREATE TABLE
syntax, but adding the ENGINE = iceberg
clause.
The commit_checkpoint_interval
parameter controls how frequently (every N checkpoints) RisingWave commits changes to the Iceberg table, creating a new Iceberg snapshot. The default value is 60. Typically, the checkpoint time is 1s. That means RisingWave will commit changes to the Iceberg table every 60s.
The approximate time to commit to Iceberg can be calculated as time = barrier_interval_ms × checkpoint_frequency × commit_checkpoint_interval
. barrier_interval_ms
and checkpoint_frequency
are system parameters that define the base checkpointing rate; commit_checkpoint_interval
is configurable in the Iceberg table engine.
INSERT
statements and query using SELECT
. You can use them as base tables to create materialized views or join them with regular tables. However, RisingWave doesn’t support renaming or changing the schemas of natively managed Iceberg tables.
rest
catalog type. You must provide your AWS credentials and specify the necessary S3 Tables REST catalog configurations.
Required REST Catalog Parameters:
Parameter Name | Description | Value for S3 Tables |
---|---|---|
catalog.rest.signing_region | The AWS region for signing REST catalog requests. | e.g., us-east-1 |
catalog.rest.signing_name | The service name for signing REST catalog requests. | s3tables |
catalog.rest.sigv4_enabled | Enables SigV4 signing for REST catalog requests. Set to true . | true |
<...>
with your specific configuration details.ENGINE = iceberg
. These tables will be registered in your specified Amazon S3 Tables catalog.
my_iceberg_table
using the Iceberg format, with metadata stored and accessible via Amazon S3 Tables.
FOR SYSTEM_TIME AS OF
or FOR SYSTEM_VERSION AS OF
clauses.
storage
, jdbc
, glue
, rest
)public.users_iceberg
in RisingWave would be accessed as table users_iceberg
within the public namespace/database in the configured Iceberg catalog by an external tool.
commit_checkpoint_interval
), can lead to many small files. You may need to run compaction procedures manually using external tools that operate on Iceberg tables to optimize read performance. We are actively working on integrating compaction features.