Re: [DISCUSS] KIP-326: Schedulable KTable as Graph source

2018-07-04 Thread flaviostutz
John, that was fantastic, man! Have you built any custom implementation of your KIP in your machine so that I could test it out here? I wish I could test it out. If you need any help implementing this feature, please tell me. Thanks. -Flávio Stutz On 2018/07/03 18:04:52, John Roesler

Re: [DISCUSS] KIP-326: Schedulable KTable as Graph source

2018-07-03 Thread flaviostutz
Great feature you have there! I'll try to exercise here how we would achieve the same functional objectives using your KIP: EXERCISE 1: - The case is "total counting of events for a huge website" - Tasks from Application A will have something like: .stream(/site-events)

Re: [DISCUSS] KIP-326: Schedulable KTable as Graph source

2018-07-02 Thread flaviostutz
Thanks for clarifying the real usage of KIP-328. Now I understood a bit better. I didn't see how that feature would be used to minimize the number of publications to the single partitioned output topic. When it is falls into supression, the graph stops going down? Could you explain better? If

Re: [DISCUSS] KIP-326: Schedulable KTable as Graph source

2018-07-01 Thread flaviostutz
For what I understood, that KIP is related to how KStreams will handle KTable updates in Windowed scenarios to optimize resource usage. I couldn't see any specific relation to this KIP. Had you? -Flávio Stutz On 2018/06/29 18:14:46, "Matthias J. Sax" wrote: > Flavio, > > thanks for cleaning

Re: [DISCUSS] KIP-326: Schedulable KTable as Graph source

2018-07-01 Thread flaviostutz
> I agree with Guozhang on comparing the pros and cons of the approach he > outlined vs the one in the proposed KIP. I've just replied him. Please take a look. > Will the triggering mechanism always be time, or would it make sense to > expand to use other mechanisms such as the number of records,

Re: [DISCUSS] KIP-326: Schedulable KTable as Graph source

2018-07-01 Thread flaviostutz
Cons: We tried the "single partition" strategy, but the problem is that for each incoming message to the Graph, we have another output message with the aggregated (cummulative or not) result, so that if we have a million messages/s (among all parallel tasks) being processed, we'll have another

Re: [DISCUSS] KIP-323: Schedulable KTable as Graph source

2018-06-29 Thread flaviostutz
Guozhang, Please go to https://lists.apache.org/thread.html/e93499c918df3a3985c6da8e0f240e286f7ba321b6e532705f994a59@%3Cdev.kafka.apache.org%3E so we can continue this thread. Someone else got this KIP number while I was registering it, so the actual number is KIP-326. I already copied your

Re: [DISCUSS] KIP-326: Schedulable KTable as Graph source

2018-06-29 Thread flaviostutz
Just copying a follow up from another thread to here (sorry about the mess): From: Guozhang Wang Subject: Re: [DISCUSS] KIP-323: Schedulable KTable as Graph source Date: 2018/06/25 22:24:17 List: dev@kafka.apache.org Flávio, thanks for creating this KIP. I think this "single-aggregation" use