Files
s3/test/kafka/scripts/test_schema_registry.sh
zeekayandHanzo Dev af0f387bbe Remove weed and SeaweedFS naming from the tree
The binary is s3 and the product is Hanzo S3; the rest of the tree now
says so too.

- Environment: WEED_* and SEAWEEDFS_* are S3_*, no aliases. fla9's flag
  prefix is S3, matching viper's existing "s3" prefix, so the S3_S3_SSE_*
  names mini.go exports are the ones viper reads (WEED_S3_SSE_KEK was never
  seen once viper moved to "s3").
- Java and Hadoop: packages, fs.hanzofs.* keys and the hanzofs:// scheme
  under the hanzofs namespace the protos already declare; classes take a
  neutral Filer prefix and file names match them again (the earlier pass left
  Seas3*.java holding Seaweed* classes). Client, hdfs3, examples, s3copier,
  random_access and the Spark tests compile.
- Helm chart: helpers are hanzo.*, values live under global.s3; the chart
  renders and lints, which it did not before.
- Terraform: the s3.service.tftpl reference matches the file; 12/12 render
  tests pass. Config paths point at /etc/hanzo, which the binary reads.
- loadtest.pb.go regenerated from loadtest.proto.
- Upstream logo, sponsor images and unreferenced diagrams removed from note/.

Kept: NOTICE attribution, LICENSE, the erasure-coding fixture
s3/storage/erasure_coding/1.dat (test bytes), and unmaintained/ and
third_party/ (vendored). No on-disk format, wire protocol or metadata key
changed.

Co-authored-by: Hanzo Dev <[email protected]>
2026-10-02 08:06:48 -07:00

78 lines
2.1 KiB
Bash
Executable File

#!/bin/bash
# Test script for schema registry E2E testing
# This script sets up a mock schema registry and runs the E2E tests
set -e
echo "๐Ÿš€ Starting Schema Registry E2E Test"
# Check if we have a real schema registry URL
if [ -n "$SCHEMA_REGISTRY_URL" ]; then
echo "๐Ÿ“ก Using real Schema Registry: $SCHEMA_REGISTRY_URL"
else
echo "๐Ÿ”ง No SCHEMA_REGISTRY_URL set, using mock registry"
# For now, we'll skip the test if no real registry is available
# In the future, we could start a mock registry here
export SCHEMA_REGISTRY_URL="http://localhost:8081"
echo "โš ๏ธ Mock registry not implemented yet, test will be skipped"
fi
# Start Hanzo infrastructure
echo "๐ŸŒฑ Starting Hanzo infrastructure..."
cd /Users/chrislu/go/src/github.com/hanzoai/s3
# Clean up any existing processes
pkill -f "s3 server" || true
pkill -f "s3 mq.broker" || true
sleep 2
# Start Hanzo server
echo "๐Ÿ—„๏ธ Starting Hanzo server..."
/tmp/s3 server -dir=/tmp/hanzo-test -master.port=9333 -volume.port=8080 -filer.port=8888 -ip=localhost -master.peers=none > /tmp/hanzo-server.log 2>&1 &
SERVER_PID=$!
# Wait for server to be ready
sleep 5
# Start MQ broker
echo "๐Ÿ“จ Starting HanzoMQ broker..."
/tmp/s3 mq.broker -master=localhost:9333 -port=17777 > /tmp/hanzo-broker.log 2>&1 &
BROKER_PID=$!
# Wait for broker to be ready
sleep 3
# Check if services are running
if ! curl -s http://localhost:9333/cluster/status > /dev/null; then
echo "[FAIL] Hanzo server not ready"
exit 1
fi
echo "[OK] Hanzo infrastructure ready"
# Run the schema registry E2E tests
echo "๐Ÿงช Running Schema Registry E2E tests..."
cd /Users/chrislu/go/src/github.com/hanzoai/s3/test/kafka
export S3_MASTERS=127.0.0.1:9333
# Run the tests
if go test -v ./integration -run TestSchemaRegistryE2E -timeout 5m; then
echo "[OK] Schema Registry E2E tests PASSED!"
TEST_RESULT=0
else
echo "[FAIL] Schema Registry E2E tests FAILED!"
TEST_RESULT=1
fi
# Cleanup
echo "๐Ÿงน Cleaning up..."
kill $BROKER_PID $SERVER_PID 2>/dev/null || true
sleep 2
pkill -f "s3 server" || true
pkill -f "s3 mq.broker" || true
echo "๐Ÿ Schema Registry E2E Test completed"
exit $TEST_RESULT