Yes.
See my answer below: it highlights the difference between joining two
KTables (only primary key join) and KStream-KTable join (even if I did
mention KStream-GlobalKTable join for this case).
However, KStream-KTable joins are not symmetric, because updates to
KTable do not trigger a join comp
If I KStream.leftJoin(Ktable) this article (
https://www.confluent.io/blog/distributed-real-time-joins-and-aggregations-on-user-activity-events-using-kafka-streams/)
seems to suggest that I could have one:many. (ktable:kstream)
Accurate?
On Mon, Jan 30, 2017 at 4:35 PM, Matthias J. Sax
wrote:
If you join two KTables, one-to-many join is currently not supported
(only one-to-one, ie, primary key join).
In upcoming 0.10.2 there will be global-KTables that allow something
similar to one-to many joins -- however, only for KStream-GlobalKTable
joins, so not sure if this can help you.
About
I want to do a one:many join between two streams. There should be ~ 1:100
with < 1% having no match.
My topology is relatively simple:
KTable1.join(KTable2)->to("other topic")
\
\---> toStream().print()
In the join it takes both Value1 and Value2 as JSON, converts
