Thank you for this KIP, the motivation makes sense to me, left some questions:
1. If strategy=safe_latest and there is not committed offset, we have 2 choices based on whether the group is started newly, can you elaborate on how can we decide the group is started newly? It would be clear. 2. If strategy=nearest and there is not committed offset, its behavior is determined by the earliest, or latest, or safe_latest used together. can you elaborate on it more clearly? 3. Can you also add a column "current reset behavior” and change "reset behavior” to “proposed reset behavior”, then we can be clear that this has no effect on current behavior. 4. You added a new config “nearest.offset.reset” and only explain what will happen when we set it true, you’d better explain what will happen it it is false -- Best, Ziming > On May 26, 2022, at 10:54 AM, 胡德祺 <16120...@bjtu.edu.cn> wrote: > > Hi all, > Why is no one talking about this? > best > hudeqi > > 2022-05-23 17:45:53"胡德祺" <16120...@bjtu.edu.cn>写道： > > Hi all, > > I have written a new KIPto add some group offset reset mechanisms. Please > take a look here: https://cwiki.apache.org/confluence/x/xhyhD > > besthudeqi
