I think it is an appropriate to support multi-way joins of KTables
(including outer, left), but it is not necessarily an extension of the
"co-group" syntax. We can start this discussion as a separate KIP.
Guozhang
Hi Guozhang
Thank you very much for your response.
Since KStream does not have an aggregate method, I guess you meant:
"builder.stream("customer").groupByKey()", which can then be used in the
CoGroup, and there I'd probably need an aggregation like this:
(Long key, Customer value, Customer agg) ->
Hello Murilo,
Thanks for your interests in KIP-150.
As we discussed in the KIP, the scope of this co-group is for stream
co-aggregation. For your case, the first joining table is not from the
aggregation but is a source table itself, in this case it cannot be
included in the co-group of KIP-150.
