Skip to main content
If your goal is to create an append-only sink, you can use the emit-on-window-close policy when creating the materialized view that you want to sink data from. For details about the policy, see Emit on window close.

Syntax

Parameters

Please distinguish between the parameters set in the FORMAT and ENCODE options and those set in the WITH clause. Ensure that you place them correctly and avoid any misuse.

Backfill and isolation

When creating a sink, RisingWave will backfill historical data from the upstream source, table, or materialized view (unless snapshot=false is specified). Snapshot backfill is enabled by default to improve isolation between the backfill phase and streaming phase. This helps prevent resource contention between backfilling historical data and processing new streaming data. To disable it if needed, set SET streaming_use_snapshot_backfill=false; before creating the sink. For more details, see View and configure runtime parameters. In RisingWave Cloud, you can offload sink backfill to dedicated serverless backfiller nodes. Enable it for the current session with SET enable_serverless_backfill = true; or for one statement with WITH (cloud.serverless_backfill_enabled = true). For setup and limitations, see Serverless backfilling.

Supported sinks

Click a sink name to see the SQL syntax, options, and sample statement of sinking data from RisingWave to the sink.

See also

Overview of data delivery

DROP SINK

Remove a sink

REPLACE SINK

Replace an existing sink

SHOW CREATE SINK

Show the SQL statement used to create a sink

CREATE SINK INTO

Create a sink into RisingWave’s table
Timestamptz values are stored in UTC.When sinking downstream, the representation of timestamptz is configurable. By default, it is in the format 2023-11-11T18:30:09.453000Z.