Hey everyone,
Just created a KIP on sharing statestore state across multiple applications
without duplicating the data on multiple changelog topics. Have a look and tell
me what you think or what to improve. This is my first one, so please be gentle
Thanks for the RC, David.
I was able to successfully complete the following:
- Installed 3.1.0 RC1 and performed quickstart for broker and Connect
(using Java 17)
- Verified signatures and checksums
- Verified the tag
- Manually compared the release notes to JIRA
- Build release archive from the
Hey Nick,
Thanks for the KIP. I am maybe late to the game here, but maybe it might be
beneficial to mention a couple of example scenarios on how the values of
commit.interval.ms and this new config could affect the overall behavior .
Like what happens if the 2 values are very similar v/s if one
Please remove me from the contributors' list. I suspect that this is what
makes me receive all these emails and I have not participated to this
project in about 5 years.
My contributions have been reviewed by Guozhang Wang.
Thanks,
Phil Derome
On Sat, Jan 15, 2022 at 6:16 AM Sayantanu Dey
Hi Nick,
Thanks for the KIP!
+1 (non-binding)
Luke
On Sat, Jan 15, 2022 at 4:55 AM Matthias J. Sax wrote:
> +1 (binding)
>
> On 1/14/22 06:32, John Roesler wrote:
> > Thanks for the KIP, Nick!
> >
> > +1 (binding)
> >
> > -John
> >
> > On Fri, Jan 14, 2022, at 07:40, Bruno Cadonna wrote:
> >>
Thank you Luke,
I fleshed my KIP according to your suggestions, mostly in the Public Interfaces
section.
Please take a review again.
Ziming Deng
> On Jan 15, 2022, at 11:09 AM, Luke Chen wrote:
>
> Hi Ziming,
>
> Thanks for the KIP!
> It's good to support fetch max timestamp in
