You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Christo Lolov (Jira)" <ji...@apache.org> on 2024/01/17 13:07:00 UTC

[jira] [Created] (KAFKA-16154) Make broker changes to return an offset for LATEST_TIERED_TIMESTAMP

Christo Lolov created KAFKA-16154:
-------------------------------------

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