Jay,

Figured it out.

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.

 From my previous example,
https://gist.github.com/bf134906f6559b0f54ad#file-gistfile1-txt-L71
should be 2

-David

messages to set their offsets
On 1/30/13 11:18 AM, Jay Kreps wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB