Move entry tracking to SegmentedJournalReader 98/110998/10
authorRobert Varga <robert.varga@pantheon.tech>
Sat, 23 Mar 2024 13:51:23 +0000 (14:51 +0100)
committerRobert Varga <robert.varga@pantheon.tech>
Mon, 25 Mar 2024 07:44:43 +0000 (08:44 +0100)
commit88a1e0bc7269500b63f519e20145ae6f751485f1
tree1349ad1c3cd2ab9ba6ee31009bdd88b665e1581b
parent926877f74ff564663d1e892cbad4c13a25e7e373
Move entry tracking to SegmentedJournalReader

We have duplicated state tracking just because JournalSegmentReader used
to provide the same API as SegmentedJournalReader.

Rehost tracking the next index and current entry into
SegmentedJournalReader, making it more obvious as to what is going on.

This allows Indexed to enforce the entry being non-null, as we do not
have to use a fake entry anymore.

JIRA: CONTROLLER-2109
Change-Id: I9ebd50fde94d695bb62315bba1b6adb1235b37f1
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
atomix-storage/src/main/java/io/atomix/storage/journal/DiskJournalSegmentReader.java
atomix-storage/src/main/java/io/atomix/storage/journal/Indexed.java
atomix-storage/src/main/java/io/atomix/storage/journal/JournalSegment.java
atomix-storage/src/main/java/io/atomix/storage/journal/JournalSegmentReader.java
atomix-storage/src/main/java/io/atomix/storage/journal/MappedJournalSegmentReader.java
atomix-storage/src/main/java/io/atomix/storage/journal/SegmentedJournalReader.java