The partitions enable scalability. Consumers and produces know which
partition records belong in based on their key (or manual assignment),
which makes it very easy to scale up your kafka cluster or a consuming
cluster.
The ordering problem is one that I have faced, and have a workaround.
Just kee
I noticed a similar effect with a test tool, which checked if the order the
records were produced in, was the same as the order in which they were
consumed. Using only one partition it works fine, but using multiple
partitions the order gets messed up. If I'm right this is by design, but I
would li
You definitely *might* see data from multiple partitions, and that won't be
uncommon once you start processing data. However, there is no guarantee.
In practice, it may be unlikely to see data for both partitions on the
first call to poll() for a simple reason: poll() will return as soon as any
da
Version: 0.9.0.1
I have a test which creates two partitions in a topic, writes data to both
partitions. Then a single consumer subscribes to the topic, verifies that
it has got the assignment of both partitions in that topic & finally issues
a poll. The firs poll always comes back with records of
