-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue when producing a message with multiple headers #994
Comments
Hmm, the encode/decode logic looks right. Can you take a look on the network and see if this is a bug happening on encode or on decode? Or maybe (though unlikely) it's a bug on the broker side? cc @wladh on the off-chance you know what could be causing this. |
The problem is with the way we copy the headers from |
Oh right. This is one of the more annoying subtleties of Go, it's bitten me before too. |
Merge fixed the issue. Thanks. |
Versions
Please specify real version numbers or git SHAs, not just "Latest" since that changes fairly regularly.
Sarama Version: 6a8d89d
Kafka Version: 1.0.0
Go Version: go1.9.2 linux/amd64
Configuration
What configuration values are you using for Sarama and Kafka?
Kafka: wurstmeister/kafka:1.0.0 docker image with default config.
Sarama: cfg.Version = sarama.V1_0_0_0
Logs
When filing an issue please provide logs from Sarama and Kafka if at all
possible. You can set
sarama.Logger
to alog.Logger
to capture Sarama debugoutput.
Producer logs:
Consumer logs:
Problem Description
When producing a message with multiple headers the last header overwrites all other headers.
Code examples:
Producer:
Consumer:
The text was updated successfully, but these errors were encountered: