Re: timestamp-oriented API

The broker maintains a timestamp index and uses this timestamp index to answer the "offsetForTimes" request. The returned offset guarantees, that there is no record with a smaller timestamp and smaller offset in the topic. Thus, if there are out-of-order records in the topic, and you start reading

Re: timestamp-oriented API

If you set *message.timestamp.type* (or *log.message.timestamp.type*) to be LogAppendTime, this would make sense. I am new to Kafka, too, and if this was set to CreateTime, I don't know what the behavior would be. There is *message.timestamp.difference.max.ms