One thing I want to do before +1 is to update the migration plan on the wiki regarding latest updates as well. Currently it states that in the second phase, the broker will "fill in the time field with current server time and re-compress the message" when it gets an older versioned produce request and "check and maybe overwrite the time field" when it gets a newer versioned produce request.
Specifically, when the timestamp type is configured as "LogCreationTime" for that topic, while a broker received an old versioned produce request, should it fill in the time field with its own "log-append-timestamp", or should it fill it in with some value like "-1" indicating the timestamp is not available? Guozhang On Tue, Dec 22, 2015 at 12:34 PM, Anna Povzner <a...@confluent.io> wrote: > Hi, > > I am opening the voting thread for KIP-32: Add CreateTime and > LogAppendTime to Kafka message. > > For reference, here's the KIP wiki: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-32+-+Add+CreateTime+and+LogAppendTime+to+Kafka+message > > And the mailing list threads: > > September: > http://mail-archives.apache.org/mod_mbox/kafka-dev/201509.mbox/%3CCAHrRUm6NMg%3DPh4HAJdxr%3DpmZhfFcD5OEV2yxj3fg%2BXnEBTW%2B3w%40mail.gmail.com%3E > > October: > http://mail-archives.apache.org/mod_mbox/kafka-dev/201510.mbox/%3CCAHrRUm7RiBAJxwO15s1tztz%3D15oibO-QJ%2B_w8AxafTnuw3jjCw%40mail.gmail.com%3E > > December: > http://mail-archives.apache.org/mod_mbox/kafka-dev/201512.mbox/%3CCAHrRUm4ugxDYzyy26MGRGKpK4hsjT4EKTuu18M3wztYq4PE%3DaQ%40mail.gmail.com%3E > > > Thanks > Anna > -- -- Guozhang
