Hi Guozhang, Apologies for the late answer. Originally that was my proposal - to piggyback on the provided materialisation method ( https://issues.apache.org/jira/browse/KAFKA-10383). John Roesler suggested to us to provide even further fine tuning on API level parameters. Maybe we could see this as two sides of the same coin:
- On the current API, we change it to piggy back on the materialization method provided to the join store. - We extend the API to allow a user to fine tune different materialization methods for subscription and join store. What do you think? Cheers, Marco On Thu, Mar 4, 2021 at 8:04 PM Guozhang Wang <wangg...@gmail.com> wrote: > Thanks Marco, > > Just a quick thought: what if we reuse the existing Materialized object for > both subscription and join stores, instead of introducing a new param / > class? > > Guozhang > > On Tue, Mar 2, 2021 at 1:07 AM Marco Aurélio Lotz <cont...@marcolotz.com> > wrote: > > > Hi folks, > > > > I would like to invite everyone to discuss further KIP-718: > > > > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-718%3A+Make+KTable+Join+on+Foreign+key+unopinionated > > > > I welcome all feedback on it. > > > > Kind Regards, > > Marco Lotz > > > > > -- > -- Guozhang >
