Files
seaweedfs/weed
chrislu edeb922749 Remove correlation ID from Metadata v1 response for kafka-go compatibility
PARTIAL FIX: Remove correlation ID from response struct for kafka-go transport layer

## Root Cause Analysis:
- kafka-go handles correlation ID at transport layer (protocol/roundtrip.go)
- kafka-go ReadResponse() reads correlation ID separately from response struct
- Our Metadata responses included correlation ID in struct, causing parsing errors
- Sarama vs kafka-go handle correlation IDs differently

## Changes:
- Removed correlation ID from Metadata v1 response struct
- Added comment explaining kafka-go transport layer handling
- Response size reduced from 92 to 88 bytes (4 bytes = correlation ID)

## Status:
- ✅ Correlation ID issue partially fixed
- ❌ kafka-go still fails with 'multiple Read calls return no data or error'
- ❌ Still uses v1 instead of negotiated v4 (suggests ApiVersions parsing issue)

## Next Steps:
- Investigate remaining Metadata v1 format issues
- Check if other response fields have format problems
- May need to fix ApiVersions response format to enable proper version negotiation

This is progress toward full kafka-go compatibility.
2025-09-12 09:58:53 -07:00
..
2025-08-09 21:47:29 -07:00
2025-07-19 23:56:17 -07:00
2025-08-30 11:15:48 -07:00
2025-08-31 23:31:28 -07:00
2025-08-22 01:15:42 -07:00
2025-09-10 11:04:42 -07:00
2025-08-30 11:15:48 -07:00
2024-06-25 09:18:11 -07:00
2025-08-30 11:15:48 -07:00
2024-02-14 08:26:38 -08:00
2025-07-19 21:43:34 -07:00
2025-03-17 23:13:27 -07:00