[
https://issues.apache.org/jira/browse/KAFKA-10269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17361464#comment-17361464
]
Dongjin Lee commented on KAFKA-10269:
-------------------------------------
[~d-t-w]
> is it difficult or expensive to return the timestamp in the case of Earliest
> or Latest Spec?
I can't be certain. AFAIK this is for a historical reason or backward
compatibility.
> In terms of API, is there any other way to identify the timestamp of the
> first or last offset?
Seek to the first or last position with Consumer. 2. Fetch a record, check the
timestamp.
> 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)
