-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
38 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -40,7 +40,7 @@ WITH ( | |
| commit\_checkpoint\_interval | Optional. Commit every N checkpoints (N > 0). Default value is 10. <br/>The behavior of this field also depends on the `sink_decouple` setting:<ul><li>If `sink_decouple` is true (the default), the default value of `commit_checkpoint_interval` is 10.</li> <li>If `sink_decouple` is set to false, the default value of `commit_checkpoint_interval` is 1.</li> <li>If `sink_decouple` is set to false and `commit_checkpoint_interval` is set to larger than 1, an error will occur.</li></ul> | | ||
| clickhouse.delete.column | Optional. You can run an upsert sink using the ReplacingMergeTree engine. When using the ReplacingMergeTree engine, you can specify the delete column with this parameter. | | ||
|
||
### Upsert sinks | ||
## Upsert sinks | ||
|
||
While RisingWave supports `append-only` sinks for all ClickHouse engines, support for `upsert` sinks is limited. Additionally, for ReplacingMergeTree engines, an `append-only` sink will not insert duplicate data. | ||
|
||
|
@@ -50,6 +50,42 @@ RisingWave supports `upsert` sinks for the following ClickHouse engines: | |
* VersionedCollapsingMergeTree: `DELETE` operations are transformed into `INSERT with SIGN = -1`. | ||
* ReplacingMergeTree: `DELETE` operations are transformed into `INSERT with SIGN = 1`. | ||
|
||
## Supported table engines | ||
|
||
RisingWave supports the following table engines of ClickHouse: | ||
|
||
* MergeTree | ||
* ReplacingMergeTree | ||
* SummingMergeTree | ||
* AggregatingMergeTree | ||
* CollapsingMergeTree | ||
* VersionedCollapsingMergeTree | ||
* GraphiteMergeTree | ||
* ReplicatedMergeTree | ||
* ReplicatedReplacingMergeTree | ||
* ReplicatedSummingMergeTree | ||
* ReplicatedAggregatingMergeTree | ||
* ReplicatedCollapsingMergeTree | ||
* ReplicatedVersionedCollapsingMergeTree | ||
* ReplicatedGraphiteMergeTree | ||
* SharedMergeTree | ||
* SharedReplacingMergeTree | ||
* SharedSummingMergeTree | ||
* SharedAggregatingMergeTree | ||
* SharedCollapsingMergeTree | ||
* SharedVersionedCollapsingMergeTree | ||
* SharedGraphiteMergeTree | ||
|
||
Among these, engines prefixed with "Shared" are exclusively available in ClickHouse Cloud and are premium features in RisingWave. They provide enhanced capabilities for distributed deployments, automatic replication, and improved resource management. For more information about it, see [MergeTree Engine Family | ||
](https://clickhouse.com/docs/en/engines/table-engines/mergetree-family). | ||
|
||
<Tip> | ||
**PREMIUM EDITION FEATURE** | ||
|
||
This feature is only available in the premium edition of RisingWave. The premium edition offers additional advanced features and capabilities beyond the free and community editions. If you have any questions about upgrading to the premium edition, please contact our sales team at [[email protected]](mailto:[email protected]). | ||
</Tip> | ||
|
||
|
||
## Examples | ||
|
||
This section includes several examples that you can use if you want to quickly experiment with sinking data to ClickHouse. | ||
|