ijuma commented on code in PR #18633:
URL: https://github.com/apache/kafka/pull/18633#discussion_r1922661143
##########
core/src/test/scala/unit/kafka/server/KafkaApisTest.scala:
##########
@@ -3562,6 +3562,47 @@ class KafkaApisTest extends Logging {
assertEquals(Set(0), response.brokers.asScala.map(_.id).toSet)
}
+
+ /**
+ * Metadata request to fetch all topics should not result in the followings:
+ * 1) Auto topic creation
+ * 2) UNKNOWN_TOPIC_OR_PARTITION
+ *
+ * This case is testing the case that a topic is being deleted from
MetadataCache right after
+ * authorization but before checking in MetadataCache.
+ */
+ @Test
+ def
testGetAllTopicMetadataShouldNotCreateTopicOrReturnUnknownTopicPartition():
Unit = {
+ // Setup: authorizer authorizes 2 topics, but one got deleted in metadata
cache
+ metadataCache = mock(classOf[KRaftMetadataCache])
+ when(metadataCache.getAliveBrokerNodes(any())).thenReturn(List(new
Node(brokerId,"localhost", 0)))
+ when(metadataCache.getRandomAliveBrokerId).thenReturn(None)
+
+ // 2 topics returned for authorization in during handle
+ val topicsReturnedFromMetadataCacheForAuthorization =
Set("remaining-topic", "later-deleted-topic")
+
when(metadataCache.getAllTopics()).thenReturn(topicsReturnedFromMetadataCacheForAuthorization)
+ // 1 topic is deleted from metadata right at the time between
authorization and the next getTopicMetadata() call
+ when(metadataCache.getTopicMetadata(
+ ArgumentMatchers.eq(topicsReturnedFromMetadataCacheForAuthorization),
+ any[ListenerName],
+ anyBoolean,
+ anyBoolean
+ )).thenReturn(Seq(
+ new MetadataResponseTopic()
+ .setErrorCode(Errors.NONE.code)
+ .setName("remaining-topic")
+ .setIsInternal(false)
+ ))
+
+ val response = sendMetadataRequestWithInconsistentListeners(new
ListenerName("PALINTEXT"))
Review Comment:
Typo.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
