(fluss) branch main updated: [docs] Fix Gateway lakehouse quickstart setup (#4389)

[ab...@apache.org]

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

fresh-borzoni pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/fluss.git


The following commit(s) were added to refs/heads/main by this push:
     new 394b6f352 [docs] Fix Gateway lakehouse quickstart setup (#4389)
394b6f352 is described below

commit 394b6f352ba1127a2870b043d35192cb93b34003
Author: Jark Wu <ja...@apache.org>
AuthorDate: Thu Sep 17 06:48:05 2026 +0800

    [docs] Fix Gateway lakehouse quickstart setup (#4389)
    
    Use the RustFS client for bucket initialization and a versioned Apache
    Gateway image. Remove the mandatory local image build and clarify how
    to start tiering while keeping the SQL client session open.
    
    
    AI-Model: gpt-6
    AI-Contributed/Feature: 46/46
    AI-Contributed/UT: 0/0
    
    Co-authored-by: Codex <no...@openai.com>
---
 website/docs/quickstart/gateway-lakehouse.md | 46 +++++++++-------------------
 1 file changed, 14 insertions(+), 32 deletions(-)

diff --git a/website/docs/quickstart/gateway-lakehouse.md b/website/docs/quickstart/gateway-lakehouse.md
index b247977ea..b7261b61b 100644
--- a/website/docs/quickstart/gateway-lakehouse.md
+++ b/website/docs/quickstart/gateway-lakehouse.md
@@ -23,18 +23,15 @@ In this quickstart, you will:
     dark="gateway-lakehouse-dark.png"
 />
 
-:::caution Developer Preview - Fluss 1.0 (unreleased)
-Fluss Gateway is a preview feature in Fluss 1.0, which has not yet been
-released. This quickstart uses its unauthenticated `trust` mode and is
+:::caution Preview
+Fluss Gateway is a preview feature introduced in Fluss 1.0.
+This quickstart uses its unauthenticated `trust` mode and is
 intended only for local development. See
 [Fluss Gateway security](/docs/gateway/index.md#security) before planning
 a production deployment.
 
-No pre-built Docker Hub image is available yet – this guide requires
-building the Gateway image from source (see
-[Build the Gateway image](#build-the-gateway-image) below). The Gateway
-does not yet support reading records; this guide reads data back through
-Flink SQL.
+The Gateway does not yet support reading records; this guide reads data
+back through Flink SQL.
 :::
 
 ## Environment Setup
@@ -50,24 +47,6 @@ We encourage you to use a recent version of Docker and [Compose v2](https://docs
 (however, Compose v1 might work with a few adaptions).
 :::
 
-### Build the Gateway image
-
-:::note Fluss v1.0 developer preview 
-This guide covers a feature shipping in the upcoming Fluss 1.0 release.
-A pre-built Docker Hub image will be available at GA - until then,
-building it locally takes one extra step: run the script below from the
-root of your [Fluss source repository](https://github.com/apache/fluss)
-:::
-Run this from the root of your Fluss source checkout:
-```shell
-docker/fluss-gateway/build.sh
-```
-
-This compiles the Gateway inside a `rust:1.88-bookworm` builder container
-(no local Rust toolchain needed) and produces a local image tagged
-`fluss-gateway:dev`, which the Compose file below references directly. The
-first build may take several minutes.
-
 ### Starting required components
 
 1. Create a working directory for this guide.
@@ -110,16 +89,16 @@ services:
       - rustfs-data:/data
     command: /data
   rustfs-init:
-    image: minio/mc
+    image: rustfs/rc:v0.1.36
     depends_on:
       - rustfs
     entrypoint: >
       /bin/sh -c "
-      until mc alias set rustfs http://rustfs:9000 rustfsadmin rustfsadmin; do
+      until rc alias set rustfs http://rustfs:9000 rustfsadmin rustfsadmin; do
         echo 'Waiting for RustFS...';
         sleep 1;
       done;
-      mc mb --ignore-existing rustfs/fluss;
+      rc mb --ignore-existing rustfs/fluss;
       "
   #end
   coordinator-server:
@@ -187,7 +166,7 @@ services:
     image: zookeeper:3.9.2
   #begin Fluss Gateway
   gateway:
-    image: fluss-gateway:dev
+    image: apache/fluss-gateway:$FLUSS_DOCKER_VERSION$
     depends_on:
       - coordinator-server
     ports:
@@ -411,7 +390,9 @@ and combines them with any data already tiered:
 
 ## Start the Lakehouse Tiering Service
 
-Submit the Lakehouse Tiering Service as a detached Flink job:
+Keep the SQL client open. In another terminal, change to the directory
+containing `docker-compose.yml` and submit the Lakehouse Tiering Service
+as a detached Flink job:
 
 ```shell
 docker compose exec jobmanager \
@@ -431,7 +412,8 @@ The [Flink Web UI](http://localhost:8083/) should show one running tiering job.
 
 ## Verify Data in Paimon
 
-After approximately 30 seconds, inspect the Paimon snapshots:
+Return to the SQL client opened earlier. After approximately 30 seconds,
+inspect the Paimon snapshots:
 
 ```sql title="Flink SQL"
 SELECT snapshot_id, total_record_count