Browse Source
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.pull/7231/head
1 changed files with 3 additions and 5 deletions
Loading…
Reference in new issue