In Kafka v1.0.0 Java doc, the introduction about KafkaConsumer's commitAsync
function say that Offsets committed through multiple calls to this API are
guaranteed to be sent in the same order as the invocations and Corresponding
commit callbacks are also invoked in the same order. This description didn't
existed in v0.10.0.1. Does this mean that earlier versions of the client can't
guarantee that commit callbacks invoked order is same as the commitAync()
called order?
1 commitAsync(offset = 00001)
2 commitAsync(offset = 00002)
3 commitAsync(offset = 00003)
Assuming that a program calls commitAsync() in the order above , is the lastest
committed offset stored in kafka broker the third commit offset("00003") in
anywhere?
yan.chen...@embedway.com
