Thanks for the KIP. I do acknowledge that there could be gap with the “latest” setting and it could be addressed differently rather than having “earliest" offset settings. I was going through the KIP and had few comments or was not fully clear on the proposed solution If consumer restarts (app crash, bounce etc.) after dynamically adding partitions it would consume unread messages from last committed offset for existing partitions but would still miss the messages from new partition. If the offset are deleted mention in mentioned in Scenario 2 (Log truncation) how this solution would address that scenario ? Do we need to care about Clock Skew or SystemTime Issues on consumer client side. Should we use timestamp on the server/broker side ? Do you plan to have any metrics or observability when consumer resets offset by_start_time
> On Mar 5, 2026, at 06:14, 黃竣陽 <[email protected]> wrote: > > Hello everyone, > > I would like to start a discussion on KIP-1282: Prevent data loss during > partition expansion for dynamically added partitions > <https://cwiki.apache.org/confluence/x/mIY8G> > > This proposal aims to introduce a new auto.offset.reset policy by_start_time, > anchoring the > offset reset to the consumer's startup timestamp rather than partition > discovery time, to prevent > silent data loss during partition expansion. > > Best regards, > Jiunn-Yang
