This is an automated email from the ASF dual-hosted git repository.
MehulBatra pushed a commit to branch release-0.9
in repository https://gitbox.apache.org/repos/asf/fluss.git
The following commit(s) were added to refs/heads/release-0.9 by this push:
new def05840b fix broken path (#3382)
def05840b is described below
commit def05840b665fe59b89cc1d24ae06348ed01cdfb
Author: MehulBatra <[email protected]>
AuthorDate: Tue May 26 16:19:32 2026 +0530
fix broken path (#3382)
---
website/docs/streaming-lakehouse/integrate-data-lakes/iceberg.md | 8 ++++----
website/docs/streaming-lakehouse/integrate-data-lakes/lance.md | 4 ++--
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/website/docs/streaming-lakehouse/integrate-data-lakes/iceberg.md
b/website/docs/streaming-lakehouse/integrate-data-lakes/iceberg.md
index bb54356c1..65f8530e5 100644
--- a/website/docs/streaming-lakehouse/integrate-data-lakes/iceberg.md
+++ b/website/docs/streaming-lakehouse/integrate-data-lakes/iceberg.md
@@ -169,14 +169,14 @@ export HADOOP_CLASSPATH=`$HADOOP_HOME/bin/hadoop
classpath`
Follow the dependency management guidelines below for the [Prepare required
jars](maintenance/tiered-storage/lakehouse-storage.md#prepare-required-jars)
step:
##### 1. Core Fluss Components
-- **Fluss Flink Connector**: Put the Fluss Flink connector JAR into
`${FLINK_HOME}/lib` — see
[Dependencies](../../../engine-flink/getting-started.md#dependencies) for all
supported Flink versions.
+- **Fluss Flink Connector**: Put the Fluss Flink connector JAR into
`${FLINK_HOME}/lib` — see
[Dependencies](../../engine-flink/getting-started.md#dependencies) for all
supported Flink versions.
- For Flink 1.20:
[fluss-flink-1.20-$FLUSS_VERSION$.jar]($FLUSS_MAVEN_REPO_URL$/org/apache/fluss/fluss-flink-1.20/$FLUSS_VERSION$/fluss-flink-1.20-$FLUSS_VERSION$.jar)
##### 2. Remote Storage Support
If you are using remote storage, download the corresponding Fluss filesystem
JAR and place it into `${FLINK_HOME}/lib`:
-- **Amazon S3**: see [S3
Dependencies](../../../maintenance/filesystems/s3.md#dependencies)
-- **Aliyun OSS**: see [OSS
Dependencies](../../../maintenance/filesystems/oss.md#dependencies)
-- **HDFS**: see [HDFS
Dependencies](../../../maintenance/filesystems/hdfs.md#dependencies)
+- **Amazon S3**: see [S3
Dependencies](../../maintenance/filesystems/s3.md#dependencies)
+- **Aliyun OSS**: see [OSS
Dependencies](../../maintenance/filesystems/oss.md#dependencies)
+- **HDFS**: see [HDFS
Dependencies](../../maintenance/filesystems/hdfs.md#dependencies)
##### 3. Iceberg Lake Connector
- **Fluss Lake Iceberg**: Put
[fluss-lake-iceberg-$FLUSS_VERSION$.jar]($FLUSS_MAVEN_REPO_URL$/org/apache/fluss/fluss-lake-iceberg/$FLUSS_VERSION$/fluss-lake-iceberg-$FLUSS_VERSION$.jar)
into `${FLINK_HOME}/lib`
diff --git a/website/docs/streaming-lakehouse/integrate-data-lakes/lance.md
b/website/docs/streaming-lakehouse/integrate-data-lakes/lance.md
index 85f159dc1..6bc48dc40 100644
--- a/website/docs/streaming-lakehouse/integrate-data-lakes/lance.md
+++ b/website/docs/streaming-lakehouse/integrate-data-lakes/lance.md
@@ -73,9 +73,9 @@ Then, you must start the datalake tiering service to tier
Fluss's data to Lance.
](maintenance/tiered-storage/lakehouse-storage.md#start-the-datalake-tiering-service).
Although the example uses Paimon, the process is also applicable to Lance.
But in [Prepare required
jars](maintenance/tiered-storage/lakehouse-storage.md#prepare-required-jars)
step, you should follow this guidance:
-- Put the Fluss Flink connector JAR into `${FLINK_HOME}/lib`; pick the
connector matching your Flink version (see
[Dependencies](../../../engine-flink/getting-started.md#dependencies)). For
Flink 1.20, use
[fluss-flink-1.20-$FLUSS_VERSION$.jar]($FLUSS_MAVEN_REPO_URL$/org/apache/fluss/fluss-flink-1.20/$FLUSS_VERSION$/fluss-flink-1.20-$FLUSS_VERSION$.jar).
+- Put the Fluss Flink connector JAR into `${FLINK_HOME}/lib`; pick the
connector matching your Flink version (see
[Dependencies](../../engine-flink/getting-started.md#dependencies)). For Flink
1.20, use
[fluss-flink-1.20-$FLUSS_VERSION$.jar]($FLUSS_MAVEN_REPO_URL$/org/apache/fluss/fluss-flink-1.20/$FLUSS_VERSION$/fluss-flink-1.20-$FLUSS_VERSION$.jar).
- If you are using [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 (see the
[Filesystems](../../../maintenance/filesystems/overview.md) section) and also
put it into `${FLINK_HOME}/lib`.
+ you should download the corresponding Fluss filesystem JAR (see the
[Filesystems](../../maintenance/filesystems/overview.md) section) and also put
it into `${FLINK_HOME}/lib`.
- Put
[fluss-lake-lance-$FLUSS_VERSION$.jar]($FLUSS_MAVEN_REPO_URL$/org/apache/fluss/fluss-lake-lance/$FLUSS_VERSION$/fluss-lake-lance-$FLUSS_VERSION$.jar)
into `${FLINK_HOME}/lib`.
Additionally, when following the [Start Datalake Tiering
Service](maintenance/tiered-storage/lakehouse-storage.md#start-datalake-tiering-service)
guide, make sure to use Lance-specific configurations as parameters when
starting the Flink tiering job:
