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 2025/01/22 15:01:00 UTC

[jira] [Commented] (KAFKA-18619) New consumer topic metadata events should set requireMetadata flag

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

Lianet Magrans commented on KAFKA-18619:
----------------------------------------

Hey [~frankvicky] , I believe this is what's behind the failing auth tests you have, feel free to take it if you want, we should end up with the tiny fix I mention in the description,  and enabling the tests (let me know if you don't have bandwidth and I can take it too). Thanks! 

> New consumer topic metadata events should set requireMetadata flag
> ------------------------------------------------------------------
>
>                 Key: KAFKA-18619
>                 URL: https://issues.apache.org/jira/browse/KAFKA-18619
>             Project: Kafka
>          Issue Type: Bug
>          Components: consumer
>            Reporter: Lianet Magrans
>            Priority: Blocker
>              Labels: kip-848-client-support
>             Fix For: 4.0.0
>
>
> In the new asyn consumer, application events that require topic metadata should overwrite the requireSubscriptionMetadata func defined in the CompletableApplicationEvent class (returning false by default). This ensures that api calls that trigger those events receive metadata errors that may be discovered in the network layer.
> We should ensure that AbstractTopicMetadataEvent sets this to true, so that topic metadata calls like partitionsFor are aware of metadata errors.



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