diff --git a/server/src/main/java/io/druid/segment/realtime/appenderator/Appenderator.java b/server/src/main/java/io/druid/segment/realtime/appenderator/Appenderator.java
index 51708f4f31cd..7f06f86269e3 100644
--- a/server/src/main/java/io/druid/segment/realtime/appenderator/Appenderator.java
+++ b/server/src/main/java/io/druid/segment/realtime/appenderator/Appenderator.java
@@ -36,9 +36,9 @@
* both of those. It can also push data to deep storage. But, it does not decide which segments data should go into.
* It also doesn't publish segments to the metadata store or monitor handoff; you have to do that yourself!
*
- * You can provide a {@link Committer} or a Supplier of one when you call one of the methods that adds, persists, or
- * pushes data. The Committer should represent all data you have given to the Appenderator so far. This Committer will
- * be used when that data has been persisted to disk.
+ * You can provide a {@link Committer} or a Supplier of one when you call one of the methods that {@link #add},
+ * {@link #persistAll}, or {@link #push}. The Committer should represent all data you have given to the Appenderator so
+ * far. This Committer will be used when that data has been persisted to disk.
*/
public interface Appenderator extends QuerySegmentWalker, Closeable
{
@@ -73,8 +73,9 @@ default AppenderatorAddResult add(SegmentIdentifier identifier, InputRow row, Su
* Committer is guaranteed to be *created* synchronously with the call to add, but will actually be used
* asynchronously.
*
- * If committer is not provided, no metadata is persisted. If it's provided, the add, clear, persist, persistAll,
- * and push methods should all be called from the same thread to keep the metadata committed by Committer in sync.
+ * If committer is not provided, no metadata is persisted. If it's provided, {@link #add}, {@link #clear},
+ * {@link #persistAll}, and {@link #push} methods should all be called from the same thread to keep the metadata
+ * committed by Committer in sync.
*
* @param identifier the segment into which this row should be added
* @param row the row to add
@@ -128,8 +129,8 @@ AppenderatorAddResult add(
* for some reason, rows have been added that we do not actually want to hand off. Blocks until all data has been
* cleared. This may take some time, since all pending persists must finish first.
*
- * The add, clear, persist, persistAll, and push methods should all be called from the same thread to keep the
- * metadata committed by Committer in sync.
+ * {@link #add}, {@link #clear}, {@link #persistAll}, and {@link #push} methods should all be called from the same
+ * thread to keep the metadata committed by Committer in sync.
*/
void clear() throws InterruptedException;
@@ -147,50 +148,31 @@ AppenderatorAddResult add(
*/
ListenableFuture> drop(SegmentIdentifier identifier);
- /**
- * Persist any in-memory indexed data for segments of the given identifiers to durable storage. This may be only
- * somewhat durable, e.g. the machine's local disk. The Committer will be made synchronously with the call to
- * persist, but will actually be used asynchronously. Any metadata returned by the committer will be associated with
- * the data persisted to disk.
- *
- * If committer is not provided, no metadata is persisted. If it's provided, the add, clear, persist, persistAll,
- * and push methods should all be called from the same thread to keep the metadata committed by Committer in sync.
- *
- * @param identifiers segment identifiers to be persisted
- * @param committer a committer associated with all data that has been added to segments of the given identifiers so
- * far
- *
- * @return future that resolves when all pending data to segments of the identifiers has been persisted, contains
- * commit metadata for this persist
- */
- ListenableFuture