MINOR: typo in javadoc (#20113)
CI / build (push) Waiting to run Details
Fixup PR Labels / fixup-pr-labels (needs-attention) (push) Has been cancelled Details
Fixup PR Labels / fixup-pr-labels (triage) (push) Has been cancelled Details
Fixup PR Labels / needs-attention (push) Has been cancelled Details

This PR fixes a typo in the Javadoc.

---------

Signed-off-by: see-quick <maros.orsak159@gmail.com>

Reviewers: Luke Chen <showuon@gmail.com>
This commit is contained in:
Maros Orsak 2025-07-24 13:05:07 +02:00 committed by GitHub
parent fba01c42c8
commit 8614e15a28
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
6 changed files with 7 additions and 7 deletions

View File

@ -45,7 +45,7 @@ public interface CompletableEvent<T> {
* (if applicable) is passed to {@link CompletableFuture#complete(Object)}. In the case where the generic * (if applicable) is passed to {@link CompletableFuture#complete(Object)}. In the case where the generic
* bound type is specified as {@link Void}, {@code null} is provided.</li> * bound type is specified as {@link Void}, {@code null} is provided.</li>
* <li> * <li>
* Error: when the the event logic generates an error, the error is passed to * Error: when the event logic generates an error, the error is passed to
* {@link CompletableFuture#completeExceptionally(Throwable)}. * {@link CompletableFuture#completeExceptionally(Throwable)}.
* </li> * </li>
* <li> * <li>

View File

@ -70,7 +70,7 @@ If any of these are missing, see https://cwiki.apache.org/confluence/display/KAF
Some of these may be used from these previous settings loaded from {prefs_file}: Some of these may be used from these previous settings loaded from {prefs_file}:
{prefs} {prefs}
Do you have all of of these setup?""" Do you have all of these setup?"""
def release_announcement_email(release_version, contributors): def release_announcement_email(release_version, contributors):

View File

@ -236,7 +236,7 @@ public class KafkaStreams implements AutoCloseable {
* </li> * </li>
* <li> * <li>
* REBALANCING state will transit to RUNNING if all of its threads are in RUNNING state * REBALANCING state will transit to RUNNING if all of its threads are in RUNNING state
* (Note: a thread transits to RUNNING state, if all active tasks got restored are are ready for processing. * (Note: a thread transits to RUNNING state, if all active tasks got restored are ready for processing.
* Standby tasks are not considered.) * Standby tasks are not considered.)
* </li> * </li>
* <li> * <li>

View File

@ -1859,7 +1859,7 @@ public class StreamsConfig extends AbstractConfig {
if (segmentSize < batchSize) { if (segmentSize < batchSize) {
throw new IllegalArgumentException(String.format( throw new IllegalArgumentException(String.format(
"Specified topic segment size %d is is smaller than the configured producer batch size %d, this will cause produced batch not able to be appended to the topic", "Specified topic segment size %d is smaller than the configured producer batch size %d, this will cause produced batch not able to be appended to the topic",
segmentSize, segmentSize,
batchSize batchSize
)); ));

View File

@ -27,7 +27,7 @@ class ACLs:
:param additional_cluster_operations_to_grant may be set to ['Alter', 'Create'] if the cluster is secured since these are required :param additional_cluster_operations_to_grant may be set to ['Alter', 'Create'] if the cluster is secured since these are required
to create SCRAM credentials and topics, respectively to create SCRAM credentials and topics, respectively
:param security_protocol set it to explicitly determine whether we use client or broker credentials, otherwise :param security_protocol set it to explicitly determine whether we use client or broker credentials, otherwise
we use the the client security protocol unless inter-broker security protocol is PLAINTEXT, in which case we use PLAINTEXT. we use the client security protocol unless inter-broker security protocol is PLAINTEXT, in which case we use PLAINTEXT.
Then we use the broker's credentials if the selected security protocol matches the inter-broker security protocol, Then we use the broker's credentials if the selected security protocol matches the inter-broker security protocol,
otherwise we use the client's credentials. otherwise we use the client's credentials.
""" """
@ -49,7 +49,7 @@ class ACLs:
:param additional_cluster_operations_to_remove may be set to ['Alter', 'Create'] if the cluster is secured since these are required :param additional_cluster_operations_to_remove may be set to ['Alter', 'Create'] if the cluster is secured since these are required
to create SCRAM credentials and topics, respectively to create SCRAM credentials and topics, respectively
:param security_protocol set it to explicitly determine whether we use client or broker credentials, otherwise :param security_protocol set it to explicitly determine whether we use client or broker credentials, otherwise
we use the the client security protocol unless inter-broker security protocol is PLAINTEXT, in which case we use PLAINTEXT. we use the client security protocol unless inter-broker security protocol is PLAINTEXT, in which case we use PLAINTEXT.
Then we use the broker's credentials if the selected security protocol matches the inter-broker security protocol, Then we use the broker's credentials if the selected security protocol matches the inter-broker security protocol,
otherwise we use the client's credentials. otherwise we use the client's credentials.
""" """

View File

@ -55,7 +55,7 @@ public class JmxToolTest {
public static void beforeAll() throws Exception { public static void beforeAll() throws Exception {
int port = findRandomOpenPortOnAllLocalInterfaces(); int port = findRandomOpenPortOnAllLocalInterfaces();
jmxUrl = format("service:jmx:rmi:///jndi/rmi://:%d/jmxrmi", port); jmxUrl = format("service:jmx:rmi:///jndi/rmi://:%d/jmxrmi", port);
// explicitly set the hostname returned to the the clients in the remote stub object // explicitly set the hostname returned to the clients in the remote stub object
// when connecting to a multi-homed machine using RMI, the wrong address may be returned // when connecting to a multi-homed machine using RMI, the wrong address may be returned
// by the RMI registry to the client, causing the connection to the RMI server to timeout // by the RMI registry to the client, causing the connection to the RMI server to timeout
System.setProperty("java.rmi.server.hostname", "localhost"); System.setProperty("java.rmi.server.hostname", "localhost");