Re: [DISCUSS] KIP-813 Shared State Stores

:16, Daan Gertis wrote: > Hey John, > > > * 1. Am I right I’m thinking that there’s no way to enforce the > stores are actually read-only, right? It seems like the StoreBuilder > interface is too generic for that. If that’s true, I think it’s fine, > but we should be sur

Re: [VOTE] KIP-813 Shared State Stores

ems like a good addition to me. +1 (binding) Thanks, Bill On Fri, Apr 1, 2022 at 2:13 PM Matthias J. Sax wrote: > +1 (binding) > > > On 4/1/22 6:47 AM, John Roesler wrote: > > Thanks for the KIP, Daan! > > > > I’m +1 (binding) > > > > -John >

Re: [DISCUSS] KIP-813 Shared State Stores

his is correct. It's a know issue: > https://issues.apache.org/jira/browse/KAFKA-7663 > > Global-stores/KTables are designed to put the data into the store > _unmodified_. > > > -Matthias > > On 2/28/22 5:05 AM, Daan Gertis wrote: >> Updated the KIP to be more aligne

[VOTE] KIP-813 Shared State Stores

I would like to start a vote on this one: https://cwiki.apache.org/confluence/display/KAFKA/KIP-813%3A+Shareable+State+Stores Cheers, D.

Kafka Streams Issue

Hi All, We are experiencing some weird behaviour with our interactive query service implementation. This is the flow we’ve implemented: 1. kafkaStreams.queryMetadataForKey(store, key, serializer) returns for activeHost HostInfo{host='localhost', port=8562}, and standbyHosts [] for the stor

Re: [DISCUSS] KIP-813 Shared State Stores

M, Guozhang Wang wrote: > Hi Daan, > > I think for the read-only state stores you'd need ot slightly augment the > checkpointing logic so that it would still write the checkpointed offsets > while restoring from the changelogs. > > > Guozhang > > On Thu, Feb 17, 2

Re: [DISCUSS] KIP-813 Shared State Stores

Wang wrote: > Daan, > > Thanks for the replies, those make sense to me. > > On Tue, Feb 8, 2022 at 7:24 AM Daan Gertis wrote: > >> I just updated the KIP to reflect the things discussed in this thread. >> >> As for your questions Guozhang: >> >>> 1

Re: [DISCUSS] KIP-813 Shared State Stores

ions, like global stores? > 2) Are we trying to synchronize the store updates from the changelog to app > B's processing timelines, or just like what we do for global stores that we > just update the read-only stores async? > 3) If the answer to both of the above questions are the latt

RE: [DISCUSS] KIP-813 Shared State Stores

work as it could trigger quite some undesired side-effects given the current architecture of Kafka Streams). -Matthias On 1/16/22 11:52 PM, Daan Gertis wrote: > Hey everyone, > > Just created a KIP on sharing statestore state across multiple applications > without duplicat

Re: [DISCUSS] KIP-813: Replace KafkaConsumer with AdminClient in GetOffsetShell

Hey Deng, Seems like we ran into a bit of a split-brain situation here. I just created KIP-813 based on the last number in the wiki page and only now see your proposal. Should have checked here as well, sorry. Would you be able/willing to move to KIP-814 and register it on the KIP page as well

[DISCUSS] KIP-813 Shared State Stores

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 😉 https://cwiki.apache.org/confluence/x/q53k

Permission to contribute

Hey everyone, I would like to contribute a KIP that I think makes sense when building event-driven architectures at scale. I have been working with kafka for the past 6 years or so (I know, a shame I wasn’t on here sooner) and currently with a startup building a data-platform at peta-scale. We