Files
seaweedfs/test
chrislu d6f688a44f Limit Metadata API to v4 to fix kafka-go client compatibility
PARTIAL FIX: Force kafka-go to use Metadata v4 instead of v6

## Issue Identified:
- kafka-go was using Metadata v6 due to ApiVersions advertising v0-v6
- Our Metadata v6 implementation has format issues causing client failures
- Sarama works because it uses Metadata v4, not v6

## Changes:
- Limited Metadata API max version from 6 to 4 in ApiVersions response
- Added debug test to isolate Metadata parsing issues
- kafka-go now uses Metadata v4 (same as working Sarama)

## Status:
-  kafka-go now uses v4 instead of v6
-  Still has metadata loops (deeper issue with response format)
-  Produce operations work correctly
-  ReadPartitions API still fails

## Next Steps:
- Investigate why kafka-go keeps requesting metadata even with v4
- Compare exact byte format between working Sarama and failing kafka-go
- May need to fix specific fields in Metadata v4 response format

This is progress toward full kafka-go compatibility but more investigation needed.
2025-09-12 09:52:11 -07:00
..
2023-11-13 08:23:53 -08:00
2025-08-30 11:15:48 -07:00