You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Chia-Ping Tsai (Jira)" <ji...@apache.org> on 2026/10/19 18:00:00 UTC

[jira] [Updated] (KAFKA-21310) Add sugar method "join" to KafkaFuture

     [ https://issues.apache.org/jira/browse/KAFKA-21310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chia-Ping Tsai updated KAFKA-21310:
-----------------------------------
    Labels: need-kip  (was: )

> Add sugar method "join" to KafkaFuture
> --------------------------------------
>
>                 Key: KAFKA-21310
>                 URL: https://issues.apache.org/jira/browse/KAFKA-21310
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>            Priority: Minor
>              Labels: need-kip
>
> KafkaFuture is one of the oldest and most commonly used classes in our public APIs. We introduced the method {{toCompletionStage}} to reduce the gap from the modern async style. It works, but it could be better. We assumed users would use {{toCompletionStage}} to chain the pipeline, but we missed the users who prefer the blocking style in lambdas. Unfortunately, the blocking method {{get}} has checked exceptions in its signature.
> In short, this ticket introduces {{join}} to KafkaFuture. It could be a simple method with a default implementation, such as {{{}toCompletionStage().toCompletableFuture().join(){}}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)