You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using ClickHouse Sink with the ReplacingMergeTree, I think you can support CDC DELETE OPs by leveraging their newer (optional) is_delete addition. Basically, when you're creating the ReplacingMergeTree you can optionally provide a UInt8 column to signify when a record was deleted, and thus will not show up during a query which uses FINAL in its scan. This might be a good tradeoff from their CollapsingMergeTree being a little cumbersome and inefficient performance wise.
From a usability perspective, I think perhaps an optional clickhouse.delete.column (or similar) can be provided for ReplacingMergeTree that would allow upsert (or at least propagating DELETE OPs). You'd keep that column set to 0 until you want to record it deleted, in which case you'd set it to 1
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
From community slack: https://risingwave-community.slack.com/archives/C03BW71523T/p1718428447943059
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: