You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Lianet Magrans (Jira)" <ji...@apache.org> on 2024/07/18 20:21:00 UTC

[jira] [Updated] (KAFKA-17163) Revisit testSubscriptionOnInvalidTopic and testPollAuthenticationFailure for AsyncKafkaConsumer

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

Lianet Magrans updated KAFKA-17163:
-----------------------------------
    Summary: Revisit testSubscriptionOnInvalidTopic and testPollAuthenticationFailure for AsyncKafkaConsumer  (was: Revisit testSubscriptionOnInvalidTopic for AsyncKafkaConsumer)

> Revisit testSubscriptionOnInvalidTopic and testPollAuthenticationFailure for AsyncKafkaConsumer
> -----------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-17163
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17163
>             Project: Kafka
>          Issue Type: Task
>          Components: consumer
>            Reporter: Lianet Magrans
>            Priority: Major
>              Labels: consumer-threading-refactor
>
> testSubscriptionOnInvalidTopic expects the consumer throws
> InvalidTopicException on poll(ZERO), which fails for the new AsyncConsumer. We should investigate if this needs the same fix applied to other tests, to do continuous poll(ZERO) to allow for the background thread to run after a fetch event has been added in the app thread, so that related errors can be propagated in poll. See linked Jira with similar fix. 



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