Hi Navinder, Thanks for this proposal!
Regarding your question about whether to use the same policy enum or not, the underlying mechanism is the same, so I think we can just use the same AutoOffsetReset enum. Can you confirm whether setting the reset policy config on the global consumer currently works or not? Based on my reading of StreamsConfig, it looks like it would be: "global.consumer.auto.offset.reset". If that does work, would you still propose to augment the Java API? Thanks, -John On Fri, Jun 26, 2020, at 23:52, Navinder Brar wrote: > Hi, > > KIP: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-406%3A+GlobalStreamThread+should+honor+custom+reset+policy > > I have taken over this KIP since it has been dormant for a long time > and this looks important for use-cases that have large global data, so > rebuilding global stores from scratch might seem overkill in case of > InvalidOffsetExecption. > > We want to give users the control to use reset policy(as we do in > StreamThread) in case they hit invalid offsets. I have still not > decided whether to restrict this option to the same reset policy being > used by StreamThread(using auto.offset.reset config) or add another > reset config specifically for global stores > "global.auto.offset.reset" which gives users more control to choose > separate policies for global and stream threads. > > I would like to hear your opinions on the KIP. > > > -Navinder
