You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Satish Duggana (Jira)" <ji...@apache.org> on 2023/07/31 09:06:00 UTC

[jira] [Commented] (KAFKA-14972) Make KafkaConsumer usable in async runtimes

    [ https://issues.apache.org/jira/browse/KAFKA-14972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17749090#comment-17749090 ] 

Satish Duggana commented on KAFKA-14972:
----------------------------------------

[~erikvanoosten] I am removing this KIP from 3.6.0 release plan for now as it is not accepted. Please correct me if I am missing something here.

> Make KafkaConsumer usable in async runtimes
> -------------------------------------------
>
>                 Key: KAFKA-14972
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14972
>             Project: Kafka
>          Issue Type: Wish
>          Components: consumer
>            Reporter: Erik van Oosten
>            Assignee: Erik van Oosten
>            Priority: Major
>              Labels: needs-kip
>
> KafkaConsumer contains a check that rejects nested invocations from different threads (method {{{}acquire{}}}). For users that use an async runtime, this is an almost impossible requirement. Examples of async runtimes that are affected are Kotlin co-routines (see KAFKA-7143) and Zio.
> It should be possible for a thread to pass on its capability to access the consumer to another thread. See [KIP-944|https://cwiki.apache.org/confluence/x/chw0Dw] for a proposal and [https://github.com/apache/kafka/pull/13914] for an implementation.



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