Skip to content

Commit

Permalink
MINOR: Fixing gradle build during compileScala and compileTestScala (a…
Browse files Browse the repository at this point in the history
…pache#13588)

Reviewers: Chia-Ping Tsai <chia7712@gmail.com>
  • Loading branch information
vamossagar12 committed Apr 18, 2023
1 parent 3388adf commit f905a5a
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion core/src/main/java/kafka/log/remote/RemoteLogManager.java
Expand Up @@ -454,7 +454,7 @@ private void maybeUpdateReadOffset() throws RemoteStorageException {
// This is found by traversing from the latest leader epoch from leader epoch history and find the highest offset
// of a segment with that epoch copied into remote storage. If it can not find an entry then it checks for the
// previous leader epoch till it finds an entry, If there are no entries till the earliest leader epoch in leader
// epoch cache then it starts copying the segments from the earliest epoch entrys offset.
// epoch cache then it starts copying the segments from the earliest epoch entry's offset.
copiedOffsetOption = OptionalLong.of(findHighestRemoteOffset(topicIdPartition));
}
}
Expand Down
Expand Up @@ -202,7 +202,7 @@ void testStartup() {
}

// This test creates 2 log segments, 1st one has start offset of 0, 2nd one (and active one) has start offset of 150.
// The leader epochs are [0->0, 1->100, 2->200]. We are verifying
// The leader epochs are [0->0, 1->100, 2->200]. We are verifying:
// 1. There's only 1 segment copied to remote storage
// 2. The segment got copied to remote storage is the old segment, not the active one
// 3. The log segment metadata stored into remoteLogMetadataManager is what we expected, both before and after copying the log segments
Expand Down

0 comments on commit f905a5a

Please sign in to comment.