iit2009060 commented on PR #15060: URL: https://github.com/apache/kafka/pull/15060#issuecomment-1880890006
> @iit2009060 [KAFKA-15388](https://issues.apache.org/jira/browse/KAFKA-15388) is about addressing the fetch requests for tiered storage enabled topics that have compacted offsets in a partition before their cleanup policy is changed to delete. This PR only covers if the next offset is available only within the remote log segments. But there is a case when the offset is available in the subsequent local segments(not only in active local segments but in any of the local only segments) that have not yet been copied to remote storage. The solution does not address [KAFKA-15388](https://issues.apache.org/jira/browse/KAFKA-15388) completely. > > I am fine to merge this and have a followup PR for the mentioned scenario to resolve [KAFKA-15388](https://issues.apache.org/jira/browse/KAFKA-15388) addressing the compacted topics before tiered storage is enabled. @satishd Yes, as you mentioned the current PR is not covering reading from local log segments ,i.e. data not available in RemoteLogSegments and the reason can be 1. Log compaction 2. Retention As the above specific scenario touch point multiple feature and not generally a specific issue because of log compaction. The intention behind creating a separate [ticket](https://issues.apache.org/jira/browse/KAFKA-16088) is to provide a dedicated space for addressing the broader issue, encompassing scenarios beyond the scope of the current PR. However I am ok if we want to have a follow up PR to merge this. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
