diff --git a/docs/content.zh/release-notes/flink-2.3.md b/docs/content.zh/release-notes/flink-2.3.md index 8ddc99dbd9245..06635d5f6f9ef 100644 --- a/docs/content.zh/release-notes/flink-2.3.md +++ b/docs/content.zh/release-notes/flink-2.3.md @@ -90,17 +90,11 @@ CREATE FUNCTION my_func AS 'com.example.MyUdf' Flink 2.3 reworks how `SinkUpsertMaterializer` handles the case where a query's upsert key differs from the sink's primary key. Previously this required maintaining the full history of -records and could blow up state. Two changes address this: +records and could blow up state. An enhancement allows you to manage this situation: - A new `ON CONFLICT` clause with `DO NOTHING`, `DO ERROR` and `DO DEDUPLICATE` strategies makes the behavior on key conflict explicit. By default, planning now fails when the upsert and primary keys differ, requiring the user to choose a conflict strategy. -- Watermark-based record compaction is introduced to fix internal changelog disorder. The - trigger and frequency of compaction are controlled by: - - `table.exec.sink.upserts.compaction-mode` (default: `WATERMARK`) — `WATERMARK` or - `CHECKPOINT`. - - `table.exec.sink.upserts.compaction-interval` — optional fallback interval for emitting - watermarks when none arrive naturally. #### Process Table Function enhancements diff --git a/docs/content/release-notes/flink-2.3.md b/docs/content/release-notes/flink-2.3.md index 8ddc99dbd9245..06635d5f6f9ef 100644 --- a/docs/content/release-notes/flink-2.3.md +++ b/docs/content/release-notes/flink-2.3.md @@ -90,17 +90,11 @@ CREATE FUNCTION my_func AS 'com.example.MyUdf' Flink 2.3 reworks how `SinkUpsertMaterializer` handles the case where a query's upsert key differs from the sink's primary key. Previously this required maintaining the full history of -records and could blow up state. Two changes address this: +records and could blow up state. An enhancement allows you to manage this situation: - A new `ON CONFLICT` clause with `DO NOTHING`, `DO ERROR` and `DO DEDUPLICATE` strategies makes the behavior on key conflict explicit. By default, planning now fails when the upsert and primary keys differ, requiring the user to choose a conflict strategy. -- Watermark-based record compaction is introduced to fix internal changelog disorder. The - trigger and frequency of compaction are controlled by: - - `table.exec.sink.upserts.compaction-mode` (default: `WATERMARK`) — `WATERMARK` or - `CHECKPOINT`. - - `table.exec.sink.upserts.compaction-interval` — optional fallback interval for emitting - watermarks when none arrive naturally. #### Process Table Function enhancements