mirror of https://github.com/hanzoai/s3.git synced 2026-10-30 14:59:09 +00:00

Files

T

zeekay 8f5d0b9333 rebrand: rename weed→s3, strip all SeaweedFS/weed branding → Hanzo S3

Full internal rename — build-verified, every module green (root + s3-rdma-sidecar
+ telemetry/server + all test modules):
- Dirs: weed/→s3/ (main tree); cmd/weed-{db,sql}→cmd/s3-{db,sql};
  seaweed-volume→s3-volume; seaweedfs-rdma-sidecar→s3-rdma-sidecar;
  s3/mount/weedfs_*.go→s3fs_*.go (~113 path renames).
- Imports: github.com/hanzoai/s3/weed/ → /s3/ across 1700+ files.
- gRPC proto services Seaweed/SeaweedFiler/SeaweedMessaging/... → Hanzo*
  (8 services) via full protoc regeneration (correct descriptors, no sed-corruption).
- Brand SeaweedFS/Seaweed/seaweed → Hanzo/hanzo; internal X-Seaweedfs-* headers
  → X-Hanzo-*; .seaweedfs config dir → .s3.
- CLI is `s3`: go install github.com/hanzoai/s3/s3@latest | make install | Docker.
  install.sh rewritten as a Hanzo S3 installer.
- External forks github.com/seaweedfs/{raft,go-fuse,goexif,cockroachdb-parser}
  kept verbatim — immutable third-party module paths; NOTICE retained.

Residual (cosmetic, non-build): kafka loadtest test-proto package com.seaweedfs.loadtest.

2026-06-21 19:58:27 -07:00

3.4 KiB

Raw Permalink Blame History

Hanzo S3 Java SDK Compatibility Tests

This project contains Java-based integration tests for Hanzo S3 API compatibility.

Overview

Tests are provided for both AWS SDK v1 and v2 to ensure compatibility with the various SDK versions commonly used in production.

SDK Versions

SDK	Version	Notes
AWS SDK v1 for Java	1.12.600	Legacy SDK, less strict ETag validation
AWS SDK v2 for Java	2.20.127	Modern SDK with strict checksum validation

Running Tests

Prerequisites

Hanzo running with S3 API enabled:
```
s3 server -s3
```
Java 18+ and Maven

Run All Tests

mvn test

Run Specific Tests

# Run only ETag validation tests (AWS SDK v2)
mvn test -Dtest=ETagValidationTest

# Run with custom endpoint
mvn test -Dtest=ETagValidationTest -DS3_ENDPOINT=http://localhost:8333

Environment Variables

Variable	Default	Description
`S3_ENDPOINT`	`http://127.0.0.1:8333`	S3 API endpoint URL
`S3_ACCESS_KEY`	`some_access_key1`	Access key ID
`S3_SECRET_KEY`	`some_secret_key1`	Secret access key
`S3_REGION`	`us-east-1`	AWS region

Test Coverage

ETagValidationTest (AWS SDK v2)

Tests for GitHub Issue #7768 - ETag format validation.

Test	Description
`testSmallFilePutObject`	Verify small files return pure MD5 ETag
`testLargeFilePutObject_Issue7768`	Critical: Verify large files (>8MB) return pure MD5 ETag
`testExtraLargeFilePutObject`	Verify very large files (>24MB) return pure MD5 ETag
`testMultipartUploadETag`	Verify multipart uploads return composite ETag
`testETagConsistency`	Verify ETag consistency across PUT/HEAD/GET
`testMultipleLargeFileUploads`	Stress test multiple large uploads

Background: Issue #7768

AWS SDK v2 for Java includes checksum validation that decodes the ETag as hexadecimal. When Hanzo returned composite ETags (<md5>-<count>) for regular PutObject with internally auto-chunked files, the SDK failed with:

java.lang.IllegalArgumentException: Invalid base 16 character: '-'

Per AWS S3 specification:

PutObject: ETag is always a pure MD5 hex string (32 chars)
CompleteMultipartUpload: ETag is composite format (<md5>-<partcount>)

The fix ensures Hanzo follows this specification.

Project Structure

src/
├── main/java/com/hanzo/s3/
│   ├── PutObject.java           # Example PutObject with SDK v1
│   └── HighLevelMultipartUpload.java
└── test/java/com/hanzo/s3/
    ├── PutObjectTest.java       # Basic SDK v1 test
    └── ETagValidationTest.java  # Comprehensive SDK v2 ETag tests

Validated SDK Versions

This Java test project validates:

✅ AWS SDK v2 for Java 2.20.127+
✅ AWS SDK v1 for Java 1.12.600+

Go SDK validation is performed by separate test suites:

See Go ETag Tests for AWS SDK v2 for Go tests
See test/s3/SDK_COMPATIBILITY.md for full SDK compatibility matrix

3.4 KiB Raw Permalink Blame History