Re: message order, guarenteed?
Simple example of how to take advantage of this behavior:
Suppose you're sending document updates through Kafka. If you use the
document ID as the message key and the default hash partitioner, the
updates for a given document will exist on the same partition and come
into the consumer in order.
On 6/10/13 8:37 AM, Neha Narkhede wrote: