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
Just to let you guys know, this KIP was actually registered under the number
326:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-326%3A+Schedulable+KTable+as+Graph+source
On 2018/06/25 17:13:12, Flávio Stutz wrote:
> Hey, guys, I've just started a KIP discussion here:
>
>
Flávio, thanks for creating this KIP.
I think this "single-aggregation" use case is common enough that we should
consider how to efficiently supports it: for example, for KSQL that's built
on top of Streams, we've seen lots of query statements whose return is
expected a single row indicating the
This would be useful feature.
In the Public Interfaces section, the new method lacks a closing
parenthesis.
In the Proposed Changes section, if the order of the 3 bullets can match
the order of the parameters of the new method, it would be easier to read.
For Rejected Alternatives #2, can you
Hey, guys, I've just started a KIP discussion here:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-323%3A+Schedulable+KTable+as+Graph+source
