mirror of
https://github.com/hanzoai/s3.git
synced 2026-11-02 13:11:24 +00:00
zooqueen
dd74d3e6d6
hanzoai/s3 was an AGPL-3.0 MinIO fork whose network-copyleft blocks embedding
and reselling as a managed service. Replace it wholesale with a fork of
SeaweedFS (github.com/seaweedfs/seaweedfs, Apache-2.0, Go) which ships a
built-in S3 gateway + Filer.
- License: AGPL-3.0 -> Apache-2.0 (upstream LICENSE kept verbatim, incl.
"Copyright 2025 Chris Lu"); NOTICE added crediting SeaweedFS. No AGPL/BUSL/
SSPL/GPL or enterprise ("ee") files remain.
- Module: go.mod path set to github.com/hanzoai/s3 with a self-replace
(replace github.com/seaweedfs/seaweedfs => ./) so the ~1800 internal Go files
keep their upstream import paths with zero churn. Internal identifiers and
import paths are intentionally NOT renamed.
- CLI rebrand: the binary is built as `s3` (was `weed`); root usage, per-command
help/usage/flag strings, shell autocomplete program name, and the product name
in CLI output now read "Hanzo S3" / `s3`. Users never see `weed`.
(e.g. `s3 server`, `s3 filer`, `s3 master`, `s3 volume`, `s3 s3`, `s3 mount`.)
- Build: `make` (or `go build -o s3 ./weed`) builds the `s3` binary green;
`cmd/weed-db` and `cmd/weed-sql` also build; `go vet ./weed/command/` clean.
- README/LLM.md rewritten for Hanzo S3; AGENTS.md/CLAUDE.md symlinks preserved.
- Dropped a 33MB prebuilt Mach-O `stress` binary upstream had committed; `.gitignore`
updated to ignore the `s3` build output.
Dremio Iceberg Catalog Integration Test
This directory contains a Dremio integration smoke test for SeaweedFS's Iceberg REST Catalog implementation.
What It Tests
TestDremioIcebergCatalog verifies the Dremio path end to end:
- Starts a local SeaweedFS mini cluster with S3 Tables and Iceberg REST enabled.
- Creates a SeaweedFS table bucket.
- Creates an Iceberg namespace and empty table through the SeaweedFS REST catalog OAuth flow.
- Starts
dremio/dremio-oss:25.2.0. - Bootstraps a Dremio admin user and logs in.
- Creates a Dremio
RESTCATALOGsource that points at the SeaweedFS catalog. - Submits Dremio SQL through
/api/v3/sql, polls the job API, and reads job results. - Runs subtests against the SeaweedFS-backed Iceberg table:
BasicSelect: Dremio is alive and answering SQL.CountEmptyTable: catalog-to-table resolution and a scan of an empty table.ColumnProjection:SELECT id, labelsucceeds and the response schema reports both columns. Failure here means Dremio could not parse the schema returned by the SeaweedFS catalog.InformationSchemaColumns: the table's columns are exposed through Dremio's metadata layer with the expected ordinal order.InformationSchemaTables: the table is registered in Dremio'sINFORMATION_SCHEMA.MultiLevelNamespace: a 2-level Iceberg namespace (created via the REST API) is exposed by Dremio as nested folders, and a table inside it is queryable with dot-separated identifiers.ReadWrittenDataCountandReadWrittenDataValues: a separate table is populated with three rows by a PyIceberg writer container (Dockerfile.writer+append_rows.py) before Dremio bootstraps; Dremio reads the data back and the values are verified. This exercises the actual data path, not just metadata.
The PyIceberg writer image is built on demand via Docker layer caching. The first build pulls python:3.11-slim and pip-installs PyIceberg + PyArrow (~1-2 min in CI); subsequent invocations are cheap.
Running Locally
Build or install weed, then run:
cd test/s3tables/catalog_dremio
go test -v -timeout 20m .
The test requires Docker. The GitHub Actions job runs on ubuntu-22.04 and executes the test for pull requests.
Configuration
The test uses these fixed credentials for the local SeaweedFS IAM config:
- S3 access key:
AKIAIOSFODNN7EXAMPLE - S3 secret key:
wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY - Region:
us-west-2 - Warehouse bucket:
iceberg-tables
The Dremio source is configured via POST /api/v3/catalog; it is not configured in dremio.conf.
The Dremio container starts with the plugins.restcatalog.enabled support key enabled, which is required for the Iceberg REST Catalog source in Dremio OSS 25.2.
Troubleshooting
- Ensure Docker is running:
docker version - Ensure
weedis built or available onPATH - Check host-gateway routing if Dremio cannot reach SeaweedFS:
docker run --add-host host.docker.internal:host-gateway --rm alpine getent hosts host.docker.internal - Check Dremio logs from the failed test output; the harness prints the Dremio container tail on Dremio startup, source setup, or job failures.