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 2026/08/13 18:40:00 UTC
[jira] [Updated] (KAFKA-20669) Fix Consumer propagates stale TopicAuthorizationException/InvalidTopicException after subscription change
[ https://issues.apache.org/jira/browse/KAFKA-20669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lianet Magrans updated KAFKA-20669:
-----------------------------------
Component/s: consumer
> Fix Consumer propagates stale TopicAuthorizationException/InvalidTopicException after subscription change
> ---------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-20669
> URL: https://issues.apache.org/jira/browse/KAFKA-20669
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer
> Reporter: KC.H
> Assignee: KC.H
> Priority: Minor
> Fix For: 4.5.0
>
>
> Problem-maybeFailOnMetadataError and
> OffsetsRequestManager.maybeCompleteWithPreviousException propagate
> stored metadata errors without checking if they still apply to the
> consumer's current topics. After assign() or subscribe()
> switchestopics, the next AsyncPollEvent can inherit a stale
> TopicAuthorizationException or InvalidTopicException. This blocked
> the consumer group protocol rows of
> testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)