v 3, 2019 at 11:46 AM aishwarya kumar
> wrote:
>
> > This thread has been open for more than 72 hours. So far there are 2
> > binding and 1 non-binding votes, looking to conclude this quickly!!
> >
> > Best,
> > Aishwarya
> >
> > On Mon, Oct 28, 2019 at
Oct 28, 2019 at 11:58 AM aishwarya kumar
> wrote:
> >
> > Thank you,
> >
> > Two binding votes so far.
> >
> > I'll keep this thread open for a couple of days.
> >
> > Best,
> > Aishwarya
> >
> > On Thu, Oct 24, 2019, 3:05 PM Bi
Thu, Oct 24, 2019 at 12:54 PM Matthias J. Sax
> wrote:
>
> > Thanks for the KIP!
> >
> > +1 (binding)
> >
> >
> > -Matthias
> >
> > On 10/24/19 6:19 AM, aishwarya kumar wrote:
> > > Hello All,
> > >
> > >
Hello All,
After concluding discussions for this KIP, I would like to go forward with
the voting process.
Jira Ticket: https://issues.apache.org/jira/browse/KAFKA-7658
KIP :
https://cwiki.apache.org/confluence/display/KAFKA/KIP-523%3A+Add+KStream%23toTable+to+the+Streams+DSL
Thank you,
Apologies for the delay.
I have made the changes in the KIP, i'll be starting the voting process
shortly.
Best regards,
Aishwarya Kumar
On Mon, Oct 7, 2019 at 6:06 PM Matthias J. Sax
wrote:
> Aishwarya,
>
> Why is bullet point (2) formatted as "strike through"? If you
r the KIP, Aishwarya!
> -John
>
> On Fri, Sep 27, 2019 at 10:11 AM aishwarya kumar
> wrote:
> >
> > Hello John,
> >
> > Thank you for pointing this out to me, to maintain consistency across
> API's
> > it does make sense to allow users to define cu
ghts?
>
> Thanks,
> -John
>
> On Tue, Sep 24, 2019 at 9:54 AM aishwarya kumar
> wrote:
> >
> > Thank you for the suggestion Matthais, i've made the necessary changes in
> > the KIP.
> >
> > Keeping this thread open for further input.
> > KIP l
aishwarya kumar wrote:
> Thanks Matthias,
>
> That does make sense, let me update the KIP to reflect the Materialization
> scenario.
>
> Best,
> Aishwarya
>
> On Tue, Sep 17, 2019, 2:49 PM Matthias J. Sax
> wrote:
>
>> Aishwarya,
>>
>> thanks fo
use and a `storeName` or
> `StoreSupplier` is specified, the store will always be materialized and
> also be queryable. Otherwise, case (1) or (2) applies.
>
>
>
> -Matthias
>
>
> On 9/17/19 6:42 AM, aishwarya kumar wrote:
> > Hi All,
> >
> > Keeping this thre
Hi Bill,
Thanks for clarifying, and the KIP looks great!!
Best regards,
Aishwarya
On Tue, Sep 17, 2019, 6:16 PM Bill Bejeck wrote:
> Hi Aishwarya,
>
> On Tue, Sep 17, 2019 at 1:41 PM aishwarya kumar
> wrote:
>
> > Will this be applicable to Kstream-Ktable joins as well?
Will this be applicable to Kstream-Ktable joins as well? Or do users always
materialize these joins explicitly?
I'm not sure if its even necessary (or makes sense), just trying to
understand why the change is applicable to Kstream joins only?
Best,
Aishwarya
On Tue, Sep 17, 2019 at 4:05 PM Bill
ream%23toTable+to+the+Streams+DSL
jira ticket : https://issues.apache.org/jira/browse/KAFKA-7658
Best,
Aishwarya
On Fri, Sep 13, 2019 at 10:49 AM aishwarya kumar wrote:
> Hello,
>
> Starting this thread to discuss KIP-532:
> wiki link :
> https://cwiki.apache.org/confluence/display/KAFKA/K
Hello,
Starting this thread to discuss KIP-532:
wiki link :
https://cwiki.apache.org/confluence/display/KAFKA/KIP-523:+Add+KStream%23toTable+to+the+Streams+DSL
jira ticket : https://issues.apache.org/jira/browse/KAFKA-7658
There has been some discussion around the use-case of this KIP in the
13 matches
Mail list logo
