(fluss) branch release-1.0 updated: [docs] Clarify Gateway lakehouse verification steps (#4438)

[ja...@apache.org]

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

wuchong pushed a commit to branch release-1.0
in repository https://gitbox.apache.org/repos/asf/fluss.git


The following commit(s) were added to refs/heads/release-1.0 by this push:
     new 6c9513af6 [docs] Clarify Gateway lakehouse verification steps (#4438)
6c9513af6 is described below

commit 6c9513af601b125e295b0ce27ce34479b6520170
Author: Jark Wu <ja...@apache.org>
AuthorDate: Sun Sep 20 15:24:26 2026 +0800

    [docs] Clarify Gateway lakehouse verification steps (#4438)
    
    Replace the abbreviated rerun guidance with complete SQL statements and
    clarify when the unified and lake-only views expose the new record.
    
    
    AI-Model: gpt-5
    AI-Contributed/Feature: 24/24
    AI-Contributed/UT: 0/0
    
    Co-authored-by: Codex <no...@openai.com>
---
 website/docs/quickstart/gateway-lakehouse.md | 24 +++++++++++++++++++++---
 1 file changed, 21 insertions(+), 3 deletions(-)

diff --git a/website/docs/quickstart/gateway-lakehouse.md b/website/docs/quickstart/gateway-lakehouse.md
index 50d907a7b..258e7e472 100644
--- a/website/docs/quickstart/gateway-lakehouse.md
+++ b/website/docs/quickstart/gateway-lakehouse.md
@@ -456,9 +456,27 @@ curl -sS --fail-with-body -X POST \
   -d '{"entries": [{"id": "order-4", "upsert": {"order_id": 4, "customer": "Dave", "amount_cents": 2200, "status": "placed"}}]}'
 ```
 
-Re-run `SELECT ... FROM orders` in the SQL client – `order_id 4` appears
-immediately in the unified view. The lake-only view, `orders$lake`, will
-reflect it once the tiering service has processed it.
+Return to the SQL client opened earlier and query the unified view:
+
+```sql title="Flink SQL"
+SELECT order_id, customer, amount_cents, status
+FROM orders
+ORDER BY order_id;
+```
+
+`order_id = 4` appears immediately. At this point, the lake-only view is
+expected to still contain only the first three orders because the new record
+has not been tiered yet. Wait approximately 30 seconds for the next tiering
+cycle, then query the lake-only view:
+
+```sql title="Flink SQL"
+SELECT order_id, customer, amount_cents, status
+FROM orders$lake
+ORDER BY order_id;
+```
+
+After the tiering service commits the new data, the result includes
+`order_id = 4`.
 
 The two query forms serve different purposes: