I'm working on a client and I'm running into difficulties with compressed message sets. I am able to produce them fine, but when I go to fetch them, things seem strange.
I am sending a message who's value is a compressed message set. The inner message set contains a single message. Specifically what looks weird is that the key of the top message looks corrupt. Here is a trace of my payloads:
Another bit of weirdness here is how MessageSets are encoded. Everywhere else in the API, we prefix a repeated element with a size of int32. When encoding MessageSets, if I follow this convention, Kafka rejects the produce request - if I exclude that int32 it works fine. I don't know if this was intentional or not, but it is somewhat annoying and inconsistent. When decoding MessageSets, I have to do-while instead of iterate a known number of times.
MessageSets aren't size delimited because that format is shared with producer/consumer and the kafka log itself. The log itself is just a big sequence of messages and any subset that begins and ends at valid message boundaries is a valid message set. This means that message sets are size prefixed only as part of the request/response. Not sure if that is what you are asking?
It's hard to see the cause of the error you describe. I don't suppose you could send me a snapshot of your client to reproduce locally?
-Jay On Wed, Jan 30, 2013 at 7:26 AM, David Arthur <[EMAIL PROTECTED]> wrote:
In Message.scala, CurrentMagicValue is set to 0; should be 2. This was causing my client to attempt to decode it as a v0 message. Changing the value to 2 solved my problem. Seems like a trivial change, so I'll let you decided if you want a Jira or not.
On 1/30/13 4:17 PM, Jay Kreps wrote: Excellent, I shall purge my 0.7x compatible code at once :)
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext