Skip to content

Commit a437504

Browse files
authored
KAFKA-19055 Cleanup the 0.10.x information from clients module (#19320)
Removes outdated references to Kafka 0.10.x in the clients module documentation. Since the baseline version is now 2.1, any mentions of versions earlier than this are unnecessary and have been removed or updated accordingly. Changes: - Updated `ClusterResource`, `ClusterResourceListener`, and `DescribeClusterResult` Javadoc to reflect the minimum supported broker version as 2.1. - Updated `TopicConfig` documentation: Removed references to consumers older than 0.10.2. - Removed references to 0.10.x and adjusted explanations to remain relevant for newer versions. Testing & Impact: - This PR only modifies Javadoc comments—no functional code changes. - No impact on existing functionality. Reviewers: PoAn Yang <[email protected]>, Chia-Ping Tsai <[email protected]>
1 parent 6f92896 commit a437504

File tree

4 files changed

+4
-8
lines changed

4 files changed

+4
-8
lines changed

clients/src/main/java/org/apache/kafka/clients/admin/DescribeClusterResult.java

+1-2
Original file line numberDiff line numberDiff line change
@@ -61,8 +61,7 @@ public KafkaFuture<Node> controller() {
6161
}
6262

6363
/**
64-
* Returns a future which yields the current cluster id. The future value will be non-null if the
65-
* broker version is 0.10.1.0 or higher and null otherwise.
64+
* Returns a future which yields the current cluster id.
6665
*/
6766
public KafkaFuture<String> clusterId() {
6867
return clusterId;

clients/src/main/java/org/apache/kafka/common/ClusterResource.java

+2-3
Original file line numberDiff line numberDiff line change
@@ -28,8 +28,7 @@ public class ClusterResource {
2828

2929
/**
3030
* Create {@link ClusterResource} with a cluster id. Note that cluster id may be {@code null} if the
31-
* metadata request was sent to a broker without support for cluster ids. The first version of Kafka
32-
* to support cluster id is 0.10.1.0.
31+
* metadata request was sent to a broker without support for cluster ids.
3332
* @param clusterId The cluster id
3433
*/
3534
public ClusterResource(String clusterId) {
@@ -38,7 +37,7 @@ public ClusterResource(String clusterId) {
3837

3938
/**
4039
* Return the cluster id. Note that it may be {@code null} if the metadata request was sent to a broker without
41-
* support for cluster ids. The first version of Kafka to support cluster id is 0.10.1.0.
40+
* support for cluster ids.
4241
*/
4342
public String clusterId() {
4443
return clusterId;

clients/src/main/java/org/apache/kafka/common/ClusterResourceListener.java

+1-1
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@
2424
* <p>
2525
* <h4>Clients</h4>
2626
* There will be one invocation of {@link ClusterResourceListener#onUpdate(ClusterResource)} after each metadata response.
27-
* Note that the cluster id may be null when the Kafka broker version is below 0.10.1.0. If you receive a null cluster id, you can expect it to always be null unless you have a cluster with multiple broker versions which can happen if the cluster is being upgraded while the client is running.
27+
* Note the minimum supported broker version is 2.1.
2828
* <p>
2929
* {@link org.apache.kafka.clients.producer.ProducerInterceptor} : The {@link ClusterResourceListener#onUpdate(ClusterResource)} method will be invoked after {@link org.apache.kafka.clients.producer.ProducerInterceptor#onSend(org.apache.kafka.clients.producer.ProducerRecord)}
3030
* but before {@link org.apache.kafka.clients.producer.ProducerInterceptor#onAcknowledgement(org.apache.kafka.clients.producer.RecordMetadata, Exception)} .

clients/src/main/java/org/apache/kafka/common/config/TopicConfig.java

-2
Original file line numberDiff line numberDiff line change
@@ -107,8 +107,6 @@ public class TopicConfig {
107107
public static final String MAX_MESSAGE_BYTES_CONFIG = "max.message.bytes";
108108
public static final String MAX_MESSAGE_BYTES_DOC =
109109
"The largest record batch size allowed by Kafka (after compression if compression is enabled). " +
110-
"If this is increased and there are consumers older than 0.10.2, the consumers' fetch " +
111-
"size must also be increased so that they can fetch record batches this large. " +
112110
"In the latest message format version, records are always grouped into batches for efficiency. " +
113111
"In previous message format versions, uncompressed records are not grouped into batches and this " +
114112
"limit only applies to a single record in that case.";

0 commit comments

Comments
 (0)