You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Derek Troy-West (Jira)" <ji...@apache.org> on 2020/07/13 22:57:00 UTC
[jira] [Commented] (KAFKA-10269) AdminClient
ListOffsetsResultInfo/timestamp is always -1
[ https://issues.apache.org/jira/browse/KAFKA-10269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17157020#comment-17157020 ]
Derek Troy-West commented on KAFKA-10269:
-----------------------------------------
Can I add, if this is a bug I'm happy to diagnose and contribute a patch/fix. Just wondering if anyone else is experiencing the same before continuing further.
> 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)