[doc] add SeaweedFS integration doc#3607
Merged
Merged
Conversation
SeaweedFS serves both the S3 object data and the Iceberg REST catalog from the same `weed` process, with a single S3 credential pair shared across both. This page shows the minimal Doris setup; the same path is exercised end-to-end by the TestDorisIcebergCatalog integration test in the SeaweedFS repo. [fix](docs) zh: 二进制 -> 执行文件 in SeaweedFS doc [refactor](docs) reframe SeaweedFS doc benefits around stack-collapsing 2
de1730d to
e2ed11a
Compare
6 tasks
chrislusf
added a commit
to chrislusf/doris-website
that referenced
this pull request
May 15, 2026
Trim the page to match the MinIO storage page in scope: drop the SQL Catalog / Broker Load / TVF examples and the Docker block, replace with a single properties snippet. Clarify that this page covers S3 normal buckets only; S3 Table Buckets are covered by the existing Iceberg integration page (apache#3607).
chrislusf
added a commit
to chrislusf/doris-website
that referenced
this pull request
May 15, 2026
Adds a Storages page for SeaweedFS, mirroring the structure of the MinIO storage doc. Covers the `s3.*` properties Doris uses to access a SeaweedFS S3 gateway (Catalog / TVF / Broker Load / Export / Outfile), with a one-paragraph `weed mini` quick start (single-process master + volume + filer + S3). The page is scoped to SeaweedFS S3 (normal) buckets. Iceberg tables stored in SeaweedFS S3 Table Buckets are covered by the existing Integration with SeaweedFS page (apache#3607), which the page links to. Slotted under "Lakehouse > Storages > SeaweedFS", above MinIO, in sidebars-next.ts and versioned_sidebars/version-{3,4}.x-sidebars.json. English and Chinese pages for dev, 3.x, and 4.x.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Versions
Languages
Summary
Adds an Iceberg lakehouse integration page for SeaweedFS, which exposes both an S3 object endpoint and an Apache Iceberg REST Catalog from the same
weedprocess. The doc walks through:weed miniwith a single IAM config and a pre-created S3 Tables bucket.iceberg.catalog.type = "rest", where the OAuth2 client credentials and the S3 keys are the same access pair.The same end-to-end path is exercised in CI by the
TestDorisIcebergCatalogintegration test in the SeaweedFS repo (test/s3tables/catalog_doris/), which boots SeaweedFS, registers a Doris Iceberg catalog against it, writes rows via PyIceberg, and reads them back fromapache/doris:doris-all-in-one-2.1.0. The Doris catalog properties in the doc are the ones the test uses verbatim.Files
docs/,docs-next/,versioned_docs/version-3.x,versioned_docs/version-4.xi18n/zh-CN/...pathssidebars.ts,sidebars-next.ts,versioned_sidebars/version-{3,4}.x-sidebars.json—doris-seaweedfsslotted under the Iceberg Catalog category, afterdoris-lakekeeper.I'm the maintainer of SeaweedFS, so I can keep this page in sync with future changes upstream.