[docs] Use $FLUSS_VERSION$ expr in docs and fix broken links

Author: wuchong

website/docs/engine-flink/ddl.md

@@ -118,7 +118,7 @@ CREATE TABLE my_part_log_table (
 ) PARTITIONED BY (dt);
 ```
 :::note
-After the Partitioned (PrimaryKey/Log) Table is created, you need first manually create the corresponding partition using the [Add Partition](/docs/engine-flink/ddl.md#add-partition) statement
+After the Partitioned (PrimaryKey/Log) Table is created, you need first manually create the corresponding partition using the [Add Partition](engine-flink/ddl.md#add-partition) statement
 before you write/read data into this partition.
 :::
 
@@ -157,7 +157,7 @@ CREATE TABLE my_auto_part_log_table (
 );
 ```
 
-For more details about Auto Partitioned (PrimaryKey/Log) Table, refer to [Auto Partitioning Options](/docs/table-design/data-distribution/partitioning/#auto-partitioning-options).
+For more details about Auto Partitioned (PrimaryKey/Log) Table, refer to [Auto Partitioning Options](table-design/data-distribution/partitioning.md#auto-partitioning-options).
 
 ### Options
 
@@ -167,8 +167,8 @@ The supported option in "with" parameters when creating a table are as follows:
 |------------------------------------|----------|----------|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | bucket.num                         | int      | optional | The bucket number of Fluss cluster. | The number of buckets of a Fluss table.                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
 | bucket.key                         | String   | optional | (none)                              | Specific the distribution policy of the Fluss table. Data will be distributed to each bucket according to the hash value of bucket-key.  If you specify multiple fields, delimiter is ','. If the table is with primary key, you can't specific bucket key currently. The bucket keys will always be the primary key(excluding partition key). If the table is not with primary key, you can specific bucket key, and when the bucket key is not specified, the data will be distributed to each bucket randomly.  |
-| table.*                            |          |          |                                     | All the [`table.` prefix configuration](/docs/maintenance/configuration.md) are supported to be defined in "with" options.                                                                                                                                                                                                                                                                                                                                                                                         |
-| client.*                           |          |          |                                     | All the [`client.` prefix configuration](/docs/maintenance/configuration.md) are supported to be defined in "with" options.                                                                                                                                                                                                                                                                                                                                                                                        |
+| table.*                            |          |          |                                     | All the [`table.` prefix configuration](maintenance/configuration.md) are supported to be defined in "with" options.                                                                                                                                                                                                                                                                                                                                                                                         |
+| client.*                           |          |          |                                     | All the [`client.` prefix configuration](maintenance/configuration.md) are supported to be defined in "with" options.                                                                                                                                                                                                                                                                                                                                                                                        |
 
 ## Create Table Like
 

website/docs/engine-flink/getting-started.md

@@ -5,13 +5,13 @@ sidebar_position: 1
 
 # Getting Started with Flink Engine
 ## Quick Start
-For a quick introduction to running Flink, refer to the [Quick Start](/docs/quickstart/flink.md) guide.
+For a quick introduction to running Flink, refer to the [Quick Start](quickstart/flink.md) guide.
 
 
 ## Support Flink Versions
 | Fluss Connector Versions | Supported Flink Versions |
 |--------------------------|--------------------------| 
-| 0.5                      | 1.18, 1.19, 1.20         |
+| $FLUSS_VERSION_SHORT$    | 1.18, 1.19, 1.20         |
 
 
 ## Feature Support
@@ -43,10 +43,10 @@ tar -xzf flink-1.20.1-bin-scala_2.12.tgz
 Download [Fluss connector jar](/downloads#fluss-connector) and copy to the lib directory of your Flink home.
 
 ```shell
-cp fluss-connector-flink-<fluss-version>.jar <FLINK_HOME>/lib/
+cp fluss-connector-flink-$FLUSS_VERSION$.jar <FLINK_HOME>/lib/
 ```
 :::note
-If you use [Amazon S3](http://aws.amazon.com/s3/), [Aliyun OSS](https://www.aliyun.com/product/oss) or [HDFS(Hadoop Distributed File System)](https://hadoop.apache.org/docs/stable/) as Fluss's [remote storage](/docs/maintenance/tiered-storage/remote-storage), 
+If you use [Amazon S3](http://aws.amazon.com/s3/), [Aliyun OSS](https://www.aliyun.com/product/oss) or [HDFS(Hadoop Distributed File System)](https://hadoop.apache.org/docs/stable/) as Fluss's [remote storage](maintenance/tiered-storage/remote-storage.md),
 you should download the corresponding [Fluss filesystem jar](/downloads#filesystem-jars) and also copy it to the lib directory of your Flink home.
 :::
 
@@ -79,7 +79,7 @@ CREATE CATALOG fluss_catalog WITH (
 
 :::note
 1. The `bootstrap.servers` means the Fluss server address. Before you config the `bootstrap.servers`,
-   you should start the Fluss server first. See [Deploying Fluss](/docs/install-deploy/overview/#how-to-deploy-fluss)
+   you should start the Fluss server first. See [Deploying Fluss](install-deploy/overview.md#how-to-deploy-fluss)
    for how to build a Fluss cluster.
    Here, it is assumed that there is a Fluss cluster running on your local machine and the CoordinatorServer port is 9123.
 2. The` bootstrap.servers` configuration is used to discover all nodes within the Fluss cluster. It can be set with one or more (up to three) Fluss server addresses (either CoordinatorServer or TabletServer) separated by commas.

website/docs/engine-flink/lookups.md

@@ -122,7 +122,7 @@ FOR SYSTEM_TIME AS OF `o`.`ptime` AS `c`
 ON `o`.`o_custkey` = `c`.`c_custkey` AND  `o`.`o_dt` = `c`.`dt`;
 ```
 
-For more details about Fluss partitioned table, see [Partitioned Tables](/docs/table-design/data-distribution/partitioning.md).
+For more details about Fluss partitioned table, see [Partitioned Tables](table-design/data-distribution/partitioning.md).
 
 ### Lookup Options
 
@@ -266,4 +266,4 @@ ON `o`.`o_custkey` = `c`.`c_custkey` AND  `o`.`o_dt` = `c`.`dt`;
 -- join key is a prefix set of dimension table primary keys (excluding partition key) + partition key.
 ```
 
-For more details about Fluss partitioned table, see [Partitioned Tables](/docs/table-design/data-distribution/partitioning.md).
+For more details about Fluss partitioned table, see [Partitioned Tables](table-design/data-distribution/partitioning.md).

website/docs/install-deploy/deploying-distributed-cluster.md

@@ -47,8 +47,8 @@ Node1 will deploy the CoordinatorServer and one TabletServer, Node2 and Node3 wi
 Go to the [downloads page](/downloads) and download the latest Fluss release. After downloading the latest release, copy the archive to all the nodes and extract it:
 
 ```shell
-tar -xzf fluss-<fluss-version>-bin.tgz
-cd fluss-<fluss-version>/
+tar -xzf fluss-$FLUSS_VERSION$-bin.tgz
+cd fluss-$FLUSS_VERSION$/
 ```
 
 ### Configuring Fluss
@@ -86,7 +86,7 @@ tablet-server.id: 3
 
 :::note
 - `tablet-server.id` is the unique id of the TabletServer, if you have multiple TabletServers, you should set different id for each TabletServer.
-- In this example, we only set the properties that must be configured, and for some other properties, you can refer to [Configuration](/docs/maintenance/configuration/) for more details.
+- In this example, we only set the properties that must be configured, and for some other properties, you can refer to [Configuration](maintenance/configuration.md) for more details.
   :::
 
 ### Starting Fluss
@@ -121,7 +121,7 @@ Using Flink SQL Client to interact with Fluss.
 
 #### Preparation
 
-You can start a Flink standalone cluster refer to [Flink Environment Preparation](/docs/engine-flink/getting-started#preparation-when-using-flink-sql-client)
+You can start a Flink standalone cluster refer to [Flink Environment Preparation](engine-flink/getting-started.md#preparation-when-using-flink-sql-client)
 
 **Note**: Make sure the [Fluss connector jar](/downloads/) already has copied to the `lib` directory of your Flink home.
 
@@ -138,4 +138,4 @@ CREATE CATALOG fluss_catalog WITH (
 #### Do more with Fluss
 
 After the catalog is created, you can use Flink SQL Client to do more with Fluss, for example, create a table, insert data, query data, etc.
-More details please refer to [Flink Getting Started](/docs/engine-flink/getting-started/).
+More details please refer to [Flink Getting Started](engine-flink/getting-started.md).

website/docs/install-deploy/deploying-local-cluster.md

@@ -25,8 +25,8 @@ Go to the [downloads page](/downloads) and download the latest Fluss release. Ma
 package **matching your Java version**. After downloading the latest release, extract it:
 
 ```shell
-tar -xzf fluss-<fluss-version>-bin.tgz
-cd fluss-<fluss-version>/
+tar -xzf fluss-$FLUSS_VERSION$-bin.tgz
+cd fluss-$FLUSS_VERSION$/
 ```
 
 ## Starting Fluss Local Cluster
@@ -49,7 +49,7 @@ Using Flink SQL Client to interact with Fluss.
 
 #### Preparation
 
-You can start a Flink standalone cluster refer to [Flink Environment Preparation](/docs/engine-flink/getting-started#preparation-when-using-flink-sql-client)
+You can start a Flink standalone cluster refer to [Flink Environment Preparation](engine-flink/getting-started.md#preparation-when-using-flink-sql-client)
 
 **Note**: Make sure the [Fluss connector jar](/downloads/) already has copied to the `lib` directory of your Flink home.
 
@@ -66,4 +66,4 @@ CREATE CATALOG fluss_catalog WITH (
 #### Do more with Fluss
 
 After the catalog is created, you can use Flink SQL Client to do more with Fluss, for example, create a table, insert data, query data, etc.
-More details please refer to [Flink Getting started](/docs/engine-flink/getting-started/)
+More details please refer to [Flink Getting started](engine-flink/getting-started.md)

website/docs/install-deploy/deploying-with-docker.md

@@ -22,15 +22,6 @@ Recommended configuration: 4 cores, 16GB memory.
 
 Docker and the Docker Compose plugin. All commands were tested with Docker version 27.4.0 and Docker Compose version v2.30.3.
 
-**Environment Variables**
-
-Set the following environment variables in the shell where you execute the commands.
-
-```bash
-export FLUSS_VERSION=0.5.0
-export FLUSS_QUICKSTART_FLINK_VERSION=1.20-0.5
-```
-
 ## Deploy with Docker
 
 The following is a brief overview of how to quickly create a complete Fluss testing cluster
@@ -75,7 +66,7 @@ docker run \
     --env FLUSS_PROPERTIES="zookeeper.address: zookeeper:2181
 coordinator.host: coordinator-server" \
     -p 9123:9123 \
-    -d fluss/fluss:${FLUSS_VERSION} coordinatorServer
+    -d fluss/fluss:$FLUSS_VERSION$ coordinatorServer
 ```
 
 ### Start Fluss TabletServer
@@ -99,7 +90,7 @@ data.dir: /tmp/fluss/data
 remote.data.dir: /tmp/fluss/remote-data" \
     -p 9124:9124 \
     --volume shared-tmpfs:/tmp/fluss \
-    -d fluss/fluss:${FLUSS_VERSION} tabletServer
+    -d fluss/fluss:$FLUSS_VERSION$ tabletServer
 ```
 
 #### Start with Multiple TabletServer
@@ -120,7 +111,7 @@ data.dir: /tmp/fluss/data/tablet-server-0
 remote.data.dir: /tmp/fluss/remote-data" \
     -p 9124:9124 \
     --volume shared-tmpfs:/tmp/fluss \
-    -d fluss/fluss:${FLUSS_VERSION} tabletServer
+    -d fluss/fluss:$FLUSS_VERSION$ tabletServer
 ```
 
 2. start tablet-server-1
@@ -136,7 +127,7 @@ data.dir: /tmp/fluss/data/tablet-server-1
 remote.data.dir: /tmp/fluss/remote-data" \
     -p 9125:9125 \
     --volume shared-tmpfs:/tmp/fluss \
-    -d fluss/fluss:${FLUSS_VERSION} tabletServer
+    -d fluss/fluss:$FLUSS_VERSION$ tabletServer
 ```
 
 3. start tablet-server-2
@@ -152,7 +143,7 @@ data.dir: /tmp/fluss/data/tablet-server-2
 remote.data.dir: /tmp/fluss/remote-data" \
     -p 9126:9126 \
     --volume shared-tmpfs:/tmp/fluss \
-    -d fluss/fluss:${FLUSS_VERSION} tabletServer
+    -d fluss/fluss:$FLUSS_VERSION$ tabletServer
 ```
 
 Now all the Fluss related components are running.
@@ -180,7 +171,7 @@ docker run \
     --env FLINK_PROPERTIES=" jobmanager.rpc.address: jobmanager" \
     -p 8083:8081 \
     --volume shared-tmpfs:/tmp/fluss \
-    -d fluss/quickstart-flink:${FLUSS_QUICKSTART_FLINK_VERSION} jobmanager
+    -d fluss/quickstart-flink:1.20-$FLUSS_VERSION_SHORT$ jobmanager
 ```
 
 2. start taskManager
@@ -191,7 +182,7 @@ docker run \
     --network=fluss-demo \
     --env FLINK_PROPERTIES=" jobmanager.rpc.address: jobmanager" \
     --volume shared-tmpfs:/tmp/fluss \
-    -d fluss/quickstart-flink:${FLUSS_QUICKSTART_FLINK_VERSION} taskmanager
+    -d fluss/quickstart-flink:1.20-$FLUSS_VERSION_SHORT$ taskmanager
 ```
 
 #### Enter into SQL-Client
@@ -222,7 +213,7 @@ USE CATALOG fluss_catalog;
 #### Do more with Fluss
 
 After the catalog is created, you can use Flink SQL Client to do more with Fluss, for example, create a table, insert data, query data, etc.
-More details please refer to [Flink Getting started](/docs/engine-flink/getting-started/)
+More details please refer to [Flink Getting started](engine-flink/getting-started.md)
 
 ## Deploy with Docker Compose
 
@@ -237,7 +228,7 @@ You can use the following `docker-compose.yml` file to start a Fluss cluster wit
 ```yaml
 services:
   coordinator-server:
-    image: fluss/fluss:${FLUSS_VERSION}
+    image: fluss/fluss:$FLUSS_VERSION$
     command: coordinatorServer
     depends_on:
       - zookeeper
@@ -248,7 +239,7 @@ services:
         coordinator.host: coordinator-server
         remote.data.dir: /tmp/fluss/remote-data
   tablet-server:
-    image: fluss/fluss:${FLUSS_VERSION}
+    image: fluss/fluss:$FLUSS_VERSION$
     command: tabletServer
     depends_on:
       - coordinator-server
@@ -282,7 +273,7 @@ You can use the following `docker-compose.yml` file to start a Fluss cluster wit
 ```yaml
 services:
   coordinator-server:
-    image: fluss/fluss:${FLUSS_VERSION}
+    image: fluss/fluss:$FLUSS_VERSION$
     command: coordinatorServer
     depends_on:
       - zookeeper
@@ -293,7 +284,7 @@ services:
         coordinator.host: coordinator-server
         remote.data.dir: /tmp/fluss/remote-data
   tablet-server-0:
-    image: fluss/fluss:${FLUSS_VERSION}
+    image: fluss/fluss:$FLUSS_VERSION$
     command: tabletServer
     depends_on:
       - coordinator-server
@@ -309,7 +300,7 @@ services:
     volumes:
       - shared-tmpfs:/tmp/fluss
   tablet-server-1:
-    image: fluss/fluss:${FLUSS_VERSION}
+    image: fluss/fluss:$FLUSS_VERSION$
     command: tabletServer
     depends_on:
       - coordinator-server
@@ -325,7 +316,7 @@ services:
     volumes:
       - shared-tmpfs:/tmp/fluss
   tablet-server-2:
-    image: fluss/fluss:${FLUSS_VERSION}
+    image: fluss/fluss:$FLUSS_VERSION$
     command: tabletServer
     depends_on:
       - coordinator-server
@@ -371,7 +362,7 @@ The changed `docker-compose.yml` file is as follows:
 ```yaml
 services:
   coordinator-server:
-    image: fluss/fluss:${FLUSS_VERSION}
+    image: fluss/fluss:$FLUSS_VERSION$
     command: coordinatorServer
     depends_on:
       - zookeeper
@@ -382,7 +373,7 @@ services:
         coordinator.host: coordinator-server
         remote.data.dir: /tmp/fluss/remote-data
   tablet-server-0:
-    image: fluss/fluss:${FLUSS_VERSION}
+    image: fluss/fluss:$FLUSS_VERSION$
     command: tabletServer
     depends_on:
       - coordinator-server
@@ -398,7 +389,7 @@ services:
     volumes:
       - shared-tmpfs:/tmp/fluss
   tablet-server-1:
-    image: fluss/fluss:${FLUSS_VERSION}
+    image: fluss/fluss:$FLUSS_VERSION$
     command: tabletServer
     depends_on:
       - coordinator-server
@@ -414,7 +405,7 @@ services:
     volumes:
       - shared-tmpfs:/tmp/fluss
   tablet-server-2:
-    image: fluss/fluss:${FLUSS_VERSION}
+    image: fluss/fluss:$FLUSS_VERSION$
     command: tabletServer
     depends_on:
       - coordinator-server
@@ -433,7 +424,7 @@ services:
     restart: always
     image: zookeeper:3.9.2
   jobmanager:
-    image: fluss/quickstart-flink:${FLUSS_QUICKSTART_FLINK_VERSION}
+    image: fluss/quickstart-flink:1.20-$FLUSS_VERSION_SHORT$
     ports:
       - "8083:8081"
     command: jobmanager
@@ -444,7 +435,7 @@ services:
     volumes:
       - shared-tmpfs:/tmp/fluss
   taskmanager:
-    image: fluss/quickstart-flink:${FLUSS_QUICKSTART_FLINK_VERSION}
+    image: fluss/quickstart-flink:1.20-$FLUSS_VERSION_SHORT$
     depends_on:
       - jobmanager
     command: taskmanager
@@ -486,4 +477,4 @@ USE CATALOG fluss_catalog;
 #### Do more with Fluss
 
 After the catalog is created, you can use Flink SQL Client to do more with Fluss, for example, create a table, insert data, query data, etc.
-More details please refer to [Flink Getting started](/docs/engine-flink/getting-started/)
+More details please refer to [Flink Getting started](engine-flink/getting-started.md)