mirror of
https://github.com/hanzoai/s3.git
synced 2026-11-03 03:07:41 +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.
2.8 KiB
2.8 KiB
Simple Kafka-Go Publisher for SeaweedMQ
This is a simple publisher client that demonstrates publishing raw messages to SeaweedMQ topics with "_" prefix, which bypass schema validation.
Features
- Schema-Free Publishing: Topics with "_" prefix don't require schema validation
- Raw Message Storage: Messages are stored in a "value" field as raw bytes
- Multiple Message Formats: Supports JSON, binary, and empty messages
- Kafka-Go Compatible: Uses the popular kafka-go library
Prerequisites
- SeaweedMQ Running: Make sure SeaweedMQ is running on
localhost:17777(default Kafka port) - Go Modules: The project uses Go modules for dependency management
Setup and Run
# Navigate to the publisher directory
cd test/kafka/simple-publisher
# Download dependencies
go mod tidy
# Run the publisher
go run main.go
Expected Output
Publishing messages to topic '_raw_messages' on broker 'localhost:17777'
Publishing messages...
- Published message 1: {"id":1,"message":"Hello from kafka-go client",...}
- Published message 2: {"id":2,"message":"Raw message without schema validation",...}
- Published message 3: {"id":3,"message":"Testing SMQ with underscore prefix topic",...}
Publishing different raw message formats...
- Published raw message 1: key=binary_key, value=Simple string message
- Published raw message 2: key=json_key, value={"raw_field": "raw_value", "number": 42}
- Published raw message 3: key=empty_key, value=
- Published raw message 4: key=, value=Message with no key
All test messages published to topic with '_' prefix!
These messages should be stored as raw bytes without schema validation.
Topic Naming Convention
- Schema-Required Topics:
user-events,orders,payments(require schema validation) - Schema-Free Topics:
_raw_messages,_logs,_metrics(bypass schema validation)
The "_" prefix tells SeaweedMQ to treat the topic as a system topic and skip schema processing entirely.
Message Storage
For topics with "_" prefix:
- Messages are stored as raw bytes without schema validation
- No Confluent Schema Registry envelope is required
- Any binary data or text can be published
- SMQ assumes raw messages are stored in a "value" field internally
Integration with SeaweedMQ
This client works with SeaweedMQ's existing schema bypass logic:
isSystemTopic()function identifies "_" prefix topics as system topicsproduceSchemaBasedRecord()bypasses schema processing for system topics- Raw storage via
seaweedMQHandler.ProduceRecord()stores messages as-is
Use Cases
- Log ingestion: Store application logs without predefined schema
- Metrics collection: Publish time-series data in various formats
- Raw data pipelines: Process unstructured data before applying schemas
- Development/testing: Quickly publish test data without schema setup