-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Support for 0 length messages- kafka limitation or librdkafka? #60
Comments
Its an assert in librdkafka, but I dont think this is a kafka rule. |
I guess 0 is ok? We should check that compression doesn't fail ;) On Wednesday, January 15, 2014, Magnus Edenhill wrote:
|
payload length 0 is now okay, and yes, compression works for these empty messages :) |
I was surprised to get this in my callback. I'd zero is ok, it shoukdnt complain or at least should just be shown with debugging on. |
Note I don't get this callback with snappy |
Looks like the rdkafka_example cannot handle an empty message. I tried a java consumer and it's fine. |
Never mind, mistake at my end |
The gzip warning is now gone. |
There are cases where I want to send only the partition key but an empty payload. This gets rejected- is this a librdkafka limitation or a librdkafka enforcement of a kafka rule?
The text was updated successfully, but these errors were encountered: