[jira] [Commented] (KAFKA-10269) AdminClient ListOffsetsResultInfo/timestamp is always -1

["Dongjin Lee (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-10269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17357938#comment-17357938 ] 

Dongjin Lee commented on KAFKA-10269:
-------------------------------------

[~huxi_2b] It seems like this is not a bug. Reviewing the code, I found the following:

1. AdminClient#listOffsets can take OffsetSpec parameter per TopicPartition, which can be one of EarliestSpec, LatestSpec, TimestampSpec.
2. For EarliestSpec and LatestSpec, a timestamp is not returned. see: https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/log/Log.scala#L1310 Instead, -1 is returned.
3. For TimestampSpec, the designated timestamp is returned: https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/cluster/Partition.scala#L1152

I think this issue is rather a lack of documentation.

> AdminClient ListOffsetsResultInfo/timestamp is always -1
> --------------------------------------------------------
>
>                 Key: KAFKA-10269
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10269
>             Project: Kafka
>          Issue Type: Bug
>          Components: admin
>    Affects Versions: 2.5.0
>            Reporter: Derek Troy-West
>            Priority: Minor
>
> When using AdminClient/listOffsets the resulting ListOffsetResultInfos appear to always have a timestamp of -1.
> I've run listOffsets against live clusters with multiple Kafka versions (from 1.0 to 2.5) with both CreateTIme and LogAppendTime for message.timestamp.type, every result has -1 timestamp.
> e.g. 
> {{org.apache.kafka.clients.admin.ListOffsetsResult$ListOffsetsResultInfo#}}{{0x5c3a771}}
> ListOffsetsResultInfo(} offset=23016, timestamp=-1, {{leaderEpoch=Optional[0])}}
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)