[
https://issues.apache.org/jira/browse/KAFKA-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17922093#comment-17922093
]
Lianet Magrans commented on KAFKA-18619:
----------------------------------------
Merged to trunk and cherry-picked to 4.0
[https://github.com/apache/kafka/commit/52280cdb55da9070be9c50374764bb9b678b2d9b]
(all tests pass)
> 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: clients, consumer
> Reporter: Lianet Magrans
> Assignee: TengYao Chi
> 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 should allow to enable the SaslClientsWithInvalidCredentialsTest that
> are not currently running for the new consumer (and fail with attempting to
> enable them)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
