Disconnect JournalSegmentWriter from JournalWriter 46/110646/1
authorRobert Varga <robert.varga@pantheon.tech>
Mon, 11 Mar 2024 11:08:05 +0000 (12:08 +0100)
committerRobert Varga <robert.varga@pantheon.tech>
Mon, 11 Mar 2024 16:43:35 +0000 (17:43 +0100)
commitffcb297b30e62b95a90f24a2e2e7e3b06a51a75b
tree6df0759738c5cc12ae4f8e6e493922a8e3435f77
parentc87be6fb22c45480e0670c60f00226597a9d975f
Disconnect JournalSegmentWriter from JournalWriter

JournalSegmentWriter is really the internal API, so it should not have a
public API straightjacket. Disconnect the implementation, making method
properly package-private.

This also makes it very clear that JournalWriter is not something users
should close() -- because doing so would wreck internal machinery rather
thoroughly, rendering the segment writer inoperable -- and that should
only be possible via JournalSegment's lifecycle.

JIRA: CONTROLLER-2098
Change-Id: Ia18b0dc640cba11689bb36cf338c8cef3ae4e6f8
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
(cherry picked from commit 45661c71a7e3d762ceb7ac12ced3c383ba65ac76)
atomix-storage/src/main/java/io/atomix/storage/journal/FileChannelJournalSegmentWriter.java
atomix-storage/src/main/java/io/atomix/storage/journal/JournalSegmentWriter.java
atomix-storage/src/main/java/io/atomix/storage/journal/JournalWriter.java
atomix-storage/src/main/java/io/atomix/storage/journal/MappedJournalSegmentWriter.java
atomix-storage/src/main/java/io/atomix/storage/journal/SegmentedJournalWriter.java