This is an automated email from the ASF dual-hosted git repository. rndgstn pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/trunk by this push: new 66412462c8d MINOR: fix some typos in comments/docs/variable names (#13118) 66412462c8d is described below commit 66412462c8d93b62ca17d922965f039bed4807a3 Author: Ron Dagostino <rndg...@gmail.com> AuthorDate: Mon Jan 23 17:04:59 2023 -0500 MINOR: fix some typos in comments/docs/variable names (#13118) Reviewers: Colin P. McCabe <cmcc...@apache.org> --- core/src/main/scala/kafka/server/ControllerApis.scala | 10 +++++----- core/src/main/scala/kafka/server/KafkaApis.scala | 2 +- docs/ops.html | 2 +- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/core/src/main/scala/kafka/server/ControllerApis.scala b/core/src/main/scala/kafka/server/ControllerApis.scala index 1c3586263a7..5a7b5d711eb 100644 --- a/core/src/main/scala/kafka/server/ControllerApis.scala +++ b/core/src/main/scala/kafka/server/ControllerApis.scala @@ -273,10 +273,10 @@ class ControllerApis(val requestChannel: RequestChannel, idToName.put(id, nameOrError.result()) } } - // Get the list of deletable topics (those we can delete) and the list of describeable + // Get the list of deletable topics (those we can delete) and the list of describable // topics. val topicsToAuthenticate = toAuthenticate.asScala - val (describeable, deletable) = if (hasClusterAuth) { + val (describable, deletable) = if (hasClusterAuth) { (topicsToAuthenticate.toSet, topicsToAuthenticate.toSet) } else { (getDescribableTopics(topicsToAuthenticate), getDeletableTopics(topicsToAuthenticate)) @@ -289,7 +289,7 @@ class ControllerApis(val requestChannel: RequestChannel, val id = entry.getKey val name = entry.getValue if (!deletable.contains(name)) { - if (describeable.contains(name)) { + if (describable.contains(name)) { appendResponse(name, id, new ApiError(TOPIC_AUTHORIZATION_FAILED)) } else { appendResponse(null, id, new ApiError(TOPIC_AUTHORIZATION_FAILED)) @@ -301,7 +301,7 @@ class ControllerApis(val requestChannel: RequestChannel, // If so, create an error response for it. Otherwise, add it to the idToName map. controller.findTopicIds(context, providedNames).thenCompose { topicIds => topicIds.forEach { (name, idOrError) => - if (!describeable.contains(name)) { + if (!describable.contains(name)) { appendResponse(name, ZERO_UUID, new ApiError(TOPIC_AUTHORIZATION_FAILED)) } else if (idOrError.isError) { appendResponse(name, ZERO_UUID, idOrError.error) @@ -376,7 +376,7 @@ class ControllerApis(val requestChannel: RequestChannel, } } - /* The cluster metatdata topic is an internal topic with a different implementation. The user should not be + /* The cluster metadata topic is an internal topic with a different implementation. The user should not be * allowed to create it as a regular topic. */ if (topicNames.contains(Topic.CLUSTER_METADATA_TOPIC_NAME)) { diff --git a/core/src/main/scala/kafka/server/KafkaApis.scala b/core/src/main/scala/kafka/server/KafkaApis.scala index 8040d00cbe2..8666b28513b 100644 --- a/core/src/main/scala/kafka/server/KafkaApis.scala +++ b/core/src/main/scala/kafka/server/KafkaApis.scala @@ -1903,7 +1903,7 @@ class KafkaApis(val requestChannel: RequestChannel, .map(_.name) .toSet - /* The cluster metatdata topic is an internal topic with a different implementation. The user should not be + /* The cluster metadata topic is an internal topic with a different implementation. The user should not be * allowed to create it as a regular topic. */ if (topicNames.contains(Topic.CLUSTER_METADATA_TOPIC_NAME)) { diff --git a/docs/ops.html b/docs/ops.html index c3ac673fdd1..bf533f5612b 100644 --- a/docs/ops.html +++ b/docs/ops.html @@ -1197,7 +1197,7 @@ $ bin/kafka-acls.sh \ </p> <p> - <strong>Client quotas:</strong> Kafka supports different types of (per-user principal) client quotas. Because a client's quotas apply irrespective of which topics the client is writing to or reading from, they are a convenient and effective tool to allocate resources in a multi-tenant cluster. <a href="#design_quotascpu">Request rate quotas</a>, for example, help to limit a user's impact on broker CPU usage by limiting the time a broker spends on the <a href="/protocol.html">request ha [...] + <strong>Client quotas:</strong> Kafka supports different types of (per-user principal) client quotas. Because a client's quotas apply irrespective of which topics the client is writing to or reading from, they are a convenient and effective tool to allocate resources in a multi-tenant cluster. <a href="#design_quotascpu">Request rate quotas</a>, for example, help to limit a user's impact on broker CPU usage by limiting the time a broker spends on the <a href="/protocol.html">request ha [...] </p> <p>