You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2017/06/28 21:17:00 UTC

[jira] [Created] (KAFKA-5534) KafkaConsumer offsetsForTimes should include partitions in result even if no offset could be found

Jason Gustafson created KAFKA-5534:
--------------------------------------

             Summary: 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
             Fix For: 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)