Hi guys, in case of KTable with KTable joins, is co-location a requirement?
Do the 2 topics need to have the same number of partitions?
https://forum.confluent.io/t/ktable-ktable-joins-is-colocation-needed/1034
Thank you,
Nicolae
Hi Nicolae
In KStream-KStream, KStream-KTable, and KTable-KTable joins, both sides of
the join need to have the same number of partitions. Kafka Streams will
check for this, and if the number of partitions isn’t the same, Kafka
Streams will throw a TopologyException.
Foreign key joins don’t requi
Thank you John for the explanation!
I confirm that introducing a full integration I have reproduced the problem.
We have reviewed our pipelines using your suggestion (ValueTransformer and
a state store) and now it seems to work correctly!
If someone is interested here is the improved version of t
If you create a new consumer inside the assign method (and assuming you
actually
start polling with it so that it sends the JoinGroup request), then yes, it
would need a
new rebalance to accommodate this consumer. The group coordinator will
inform all the
existing members to rejoin the group so tha
Hey Peter,
It does sound like you may have hit
https://issues.apache.org/jira/browse/KAFKA-9752
You will need to upgrade your brokers in order to get the fix, since it's a
broker-side issue
On Tue, Feb 9, 2021 at 2:48 AM Péter Sinóros-Szabó
wrote:
> Hi,
>
> I have an application running with 6
