[
https://issues.apache.org/jira/browse/KAFKA-16154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869785#comment-17869785
]
Luke Chen commented on KAFKA-16154:
-----------------------------------
Gently ping [~christo_lolov] since v3.9.0 is going to be code freezed. If
you're busy, maybe we can consider to allow the community contributor to pick
it up and we just need to review the PR?
> Make broker changes to return an offset for LATEST_TIERED_TIMESTAMP
> -------------------------------------------------------------------
>
> Key: KAFKA-16154
> URL: https://issues.apache.org/jira/browse/KAFKA-16154
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Christo Lolov
> Assignee: Christo Lolov
> Priority: Major
> Fix For: 3.9.0
>
>
> A broker should start returning offsets when given a timestamp of -5, which
> signifies a LATEST_TIERED_TIMESTAMP.
> There are 3 cases.
> Tiered Storage is not enabled. In such a situation asking for
> LATEST_TIERED_TIMESTAMP should always return no offset.
> Tiered Storage is enabled and there is nothing in remote storage. In such a
> situation the offset returned should be 0.
> Tiered Storage is enabled and there is something in remote storage. In such a
> situation the offset returned should be the highest offset the broker is
> aware of.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
