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 only one partition.
I need to poll one more time to get records for the second partition. The
poll timeout has no effect on this.

Unless I've misunderstood the contract - the first poll *could* have
returned records for the both the partitions. After-all poll
returns ConsumerRecords<K,V>, which is a map of topic_partitions -->
records

I acknowledge that API does not make any hard guarantees that align with my
expectation but  looks like API was crafted to support multiple partitions
& topics in single call. Is there an implementation detail which restricts
this? Is there a configuration which is controlling what gets fetched?

--
Shrijeet

Reply via email to