[
https://issues.apache.org/jira/browse/KAFKA-15388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799416#comment-17799416
]
Divij Vaidya edited comment on KAFKA-15388 at 12/21/23 12:56 PM:
-----------------------------------------------------------------
Hey [~enether]
I will not consider this as a blocker for 3.7.0 since Tiered Storage is not
production ready in 3.7.0. We will continue to carry this bug (as we did in
3.6) until it is fixed. If we are able to fix this in timeline for 3.7, well
and good but if not, we will ship this in 3.8.
This is a blocker for TS production ready status but that will be captured
somewhere else.
was (Author: divijvaidya):
Hey [~enether]
I will not consider this as a blocker for 3.7.0 since Tiered Storage is not GA
in 3.7.0. We will continue to carry this bug (as we did in 3.6) until it is
fixed. If we are able to fix this in timeline for 3.7, well and good but if
not, we will ship this in 3.8.
> Handle topics that were having compaction as retention earlier are changed to
> delete only retention policy and onboarded to tiered storage.
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-15388
> URL: https://issues.apache.org/jira/browse/KAFKA-15388
> Project: Kafka
> Issue Type: Bug
> Reporter: Satish Duggana
> Assignee: Arpit Goyal
> Priority: Major
> Fix For: 3.7.0
>
> Attachments: Screenshot 2023-11-15 at 3.47.54 PM.png,
> tieredtopicloglist.png
>
>
> Context: [https://github.com/apache/kafka/pull/13561#discussion_r1300055517]
>
> There are 3 paths I looked at:
> * When data is moved to remote storage (1)
> * When data is read from remote storage (2)
> * When data is deleted from remote storage (3)
> (1) Does not have a problem with compacted topics. Compacted segments are
> uploaded and their metadata claims they contain offset from the baseOffset of
> the segment until the next segment's baseOffset. There are no gaps in offsets.
> (2) Does not have a problem if a customer is querying offsets which do not
> exist within a segment, but there are offset after the queried offset within
> the same segment. *However, it does have a problem when the next available
> offset is in a subsequent segment.*
> (3) For data deleted via DeleteRecords there is no problem. For data deleted
> via retention there is no problem.
>
> *I believe the proper solution to (2) is to make tiered storage continue
> looking for the next greater offset in subsequent segments.*
> Steps to reproduce the issue:
> {code:java}
> // TODO (christo)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
