Skip to content

RATIS-2642. Command API in data stream can be optional #1546

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
szetszwo merged 1 commit into from
Aug 5, 2026
+6 −1
Merged

RATIS-2642. Command API in data stream can be optional #1546

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion ratis-client/src/main/java/org/apache/ratis/client/api/DataStreamOutput.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,10 +81,15 @@ default CompletableFuture<DataStreamReply> writeAsync(File src, long position, l
* The server state machine may handle the command via its data-stream command hook
* instead of writing bytes to the data channel.
*
* This is an optional API. Implementations that do not support stream commands
* may rely on this default, which throws {@link UnsupportedOperationException}.
*
* @param command the command payload
* @return a future of the reply
*/
CompletableFuture<DataStreamReply> commandAsync(ByteBuffer command);
default CompletableFuture<DataStreamReply> commandAsync(ByteBuffer command) {
throw new UnsupportedOperationException(getClass() + " does not support commandAsync");
}

/**
* Return the future of the {@link RaftClientReply}
Expand Down
Loading