Hi Mehari, Thanks for the KIP!
The default value of *log.message.timestamp.after.max.ms <http://log.message.timestamp.after.max.ms>* is proposed to be 1 hour. Given that this is a client application breaking change, should we consider an opt-in grace period to give a proper heads up to the users? We could consider making the default as Long.MAX and printing a message that it will be made to 1 hour in the next major version bump. Subsequently, we could consider making the default as 1 hour in the next major version bump. This would ensure a smoother transition for current users. Thanks! Gaurav On Wed, Jun 21, 2023 at 1:45 PM Justine Olshan <jols...@confluent.io.invalid> wrote: > Hey Mehari, > I was just getting annoyed looking at logs of kafka clusters with timestamp > issues. Let me take final look at the KIP. > > Thanks, > Justine > > On Wed, Jun 21, 2023 at 11:13 AM Beyene, Mehari <meh...@amazon.com.invalid > > > wrote: > > > Hi Justine, > > > > I have initiated the voting process for this KIP here: > > https://lists.apache.org/thread/y3yfnphsmrgwfdhx3xfhjtwdb7p1dn0v > > We have already received two binding votes, and I am seeking a third vote > > for the adoption of the KIP. > > As you have previously reviewed this KIP, would you be willing to cast > > your vote? > > > > Please also let me know if we need to discuss more or address additional > > comments. > > > > Thanks, > > Mehari > > > > > > >
