[
https://issues.apache.org/jira/browse/KAFKA-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5534:
-------------------------------
Fix Version/s: 0.10.2.2
> KafkaConsumer offsetsForTimes should include partitions in result even if no
> offset could be found
> --------------------------------------------------------------------------------------------------
>
> Key: KAFKA-5534
> URL: https://issues.apache.org/jira/browse/KAFKA-5534
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Reporter: Jason Gustafson
> Assignee: Vahid Hashemian
> Fix For: 0.10.2.2, 0.11.0.1
>
>
> From the javadoc for {{offsetsForTimes}}:
> {code}
> * @return a mapping from partition to the timestamp and offset of the
> first message with timestamp greater
> * than or equal to the target timestamp. {@code null} will be
> returned for the partition if there is no
> * such message.
> {code}
> If the topic does not support timestamp search (i.e. magic 1 and above), we
> include the partition in the map with a null value, as described above. If
> the topic supports timestamp search but no offset could be found, we just
> leave the partition out of the map. We should make this behavior consistent
> and include the partition with a null value in the result.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
