Hi Pushkar,
The events after repartitioning are processed by a different task than
the task that read the events from the source topic. The task assignor
assigns those tasks to stream threads. So events with the same key will
be processed by the same task. As far as I understood from your earl
Thanks Bruno..
What do you mean exactly with "...and then process them in that order"?
By this, I mean to say if the order of events in partition will be
processed after repartition. Probably I don't need to go through internal
details but does the partitions of topic are again assigned to stream
Thank you both for testing this.
Fede, that's a good catch. My bad on not catching it earlier during release
prep. I will create a new RC containing the fix -
https://github.com/apache/kafka/pull/14016
--
Divij Vaidya
On Fri, Jul 14, 2023 at 9:29 AM Jakub Scholz wrote:
> +1 (non-binding). I
Hi Pushkar,
you can use repartition() for repartition your data. Method through() is
actually deprecated in favor of repartition(). Before you repartition
you need to specify the new key with selectKey().
What do you mean exactly with "...and then process them in that order"?
The order of th
+1 (non-binding). I used the staged Scala 2.13 binaries and the Maven
artifacts for my tests and all seems to work fine. Thanks.
Jakub
On Wed, Jul 12, 2023 at 12:03 PM Divij Vaidya
wrote:
> Hello Kafka users, developers and client-developers,
>
> This is the first candidate for release of Apach
