Re: Behaviour of KStreamKTableJoinProcessor

2019-07-16 Thread John Roesler
Hi again (again), Ties, Sorry for the confusion, but I was talking to someone else about this, and I started to make a ticket to fix it, and realized once I started looking into it that there is actually no repartition topic for a stream-globalTable join. So, if you do something like: = publ

Re: Behaviour of KStreamKTableJoinProcessor

2019-07-15 Thread John Roesler
Hi again, Ties, I think I spoke too soon and also misread your email. By any chance, are you doing a join of a KStream and a GlobalKTable? In this case, it would make perfect sense to do what you're doing, but unfortunately the current implementation doesn't support it. Your workaround would be

Re: Behaviour of KStreamKTableJoinProcessor

2019-07-15 Thread John Roesler
Hi Ties, You're on the right track. You need to use `KTable.map` ahead of the join to select the new key. This will allow Streams to make sure the data is correctly partitioned to perform the join. Thanks, -John On Mon, Jul 15, 2019 at 10:07 AM Ven, Ties Jens van de wrote: > > I recently starte