[
https://issues.apache.org/jira/browse/KAFKA-15169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17769103#comment-17769103
]
Arpit Goyal commented on KAFKA-15169:
-------------------------------------
[~divijvaidya] Just to confirm what I understood the flow of the first test
case
1. we call getIndexEntry
2. It throws corrupt storage exception( This exception will be thrown after
fetching from remote storage )
i.e.
{code:java}
Utils.atomicMoveWithFallback(tmpIndexFile.toPath(), indexFile.toPath(), false);
index = readIndex.apply(indexFile); // throws remote Storage exception
{code}
3. We call getIndexEntry again
4. This time file already exist on disk , it will log the corrupted error
5. It will refetch from remote storage and passes the sanity check.
The test case is basically to test the flow when corrupted file already exist
on disk ?
> Add tests for RemoteIndexCache
> ------------------------------
>
> Key: KAFKA-15169
> URL: https://issues.apache.org/jira/browse/KAFKA-15169
> Project: Kafka
> Issue Type: Test
> Reporter: Satish Duggana
> Assignee: Arpit Goyal
> Priority: Major
> Labels: KIP-405
> Fix For: 3.7.0
>
>
> Follow-up from
> https://github.com/apache/kafka/pull/13275#discussion_r1257490978
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
