(flink-web) branch asf-site updated: [hotfix][docs] Remove inconsistent parameter descriptions. (#872)

[pa...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

RocMarshal pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/flink-web.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 0a6f3ceece [hotfix][docs] Remove inconsistent parameter descriptions. (#872)
0a6f3ceece is described below

commit 0a6f3ceece26f27aa648ea125072e267e15b594e
Author: Yuepeng Pan <pa...@apache.org>
AuthorDate: Thu Jul 23 12:47:35 2026 +0800

    [hotfix][docs] Remove inconsistent parameter descriptions. (#872)
---
 docs/content/posts/2026-06-25-release-2.3.0.md | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/docs/content/posts/2026-06-25-release-2.3.0.md b/docs/content/posts/2026-06-25-release-2.3.0.md
index dde31c8501..e1b2abddb3 100644
--- a/docs/content/posts/2026-06-25-release-2.3.0.md
+++ b/docs/content/posts/2026-06-25-release-2.3.0.md
@@ -60,7 +60,7 @@ These enhancements eliminate the need to drop and recreate materialized tables w
 
 The SinkUpsertMaterializer is required when the upsert key (the unique identifier provided by the stream) is different from the primary key (the unique identifier in the target sink table). This happens in scenarios like multi-stage transformations, projections, or joins.
 
-Previously, the SinkUpsertMaterializer has had poor performance and high resource consumption because it keeps the full history of updates for the primary key, leading to unbounded state growth. Flink 2.3 addresses this with two key improvements.
+Previously, the SinkUpsertMaterializer has had poor performance and high resource consumption because it keeps the full history of updates for the primary key, leading to unbounded state growth. Flink 2.3 addresses this with an enhancement.
 
 By default, queries now fail at planning time when upsert and primary keys differ, requiring you to explicitly choose a conflict strategy. This is done with a new `ON CONFLICT` clause that makes the behavior explicit. You choose how to handle conflicts: `DO NOTHING` (silent skip), `DO ERROR` (fail the job), or `DO DEDUPLICATE` (materialize and deduplicate, similar to what Flink has done until now):
 
@@ -70,13 +70,6 @@ SELECT * FROM source
 ON CONFLICT DO DEDUPLICATE;
 ```
 
-Second, watermark-based compaction reduces state size by cleaning up old changelog records that can no longer affect the final result. Two new configuration options control the compaction behavior:
-
-  - `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.
-
 **More Information**
 * [FLIP-558](https://cwiki.apache.org/confluence/x/NoTMFw)