Newer brokers should not result in new errors for existing clients

This commit is contained in:
Ismael Juma 2025-03-20 06:29:40 -07:00 committed by GitHub
parent 4c1055e875
commit eb85eb3cbd
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions

View File

@ -61,7 +61,7 @@ import static org.apache.kafka.common.utils.Utils.propsToMap;
* The consumer is not thread-safe. See <a href="#multithreaded">Multi-threaded Processing</a> for more details. * The consumer is not thread-safe. See <a href="#multithreaded">Multi-threaded Processing</a> for more details.
* *
* <h3>Cross-Version Compatibility</h3> * <h3>Cross-Version Compatibility</h3>
* This client can communicate with brokers that are version 2.1 or newer. Older or newer brokers may not support * This client can communicate with brokers that are version 2.1 or newer. Older brokers may not support
* certain features. For example, 3.9 brokers do not support {@code subscribe(SubscriptionPattern)}, because this feature was added * certain features. For example, 3.9 brokers do not support {@code subscribe(SubscriptionPattern)}, because this feature was added
* in version 4.0. You will receive an {@link org.apache.kafka.common.errors.UnsupportedVersionException} * in version 4.0. You will receive an {@link org.apache.kafka.common.errors.UnsupportedVersionException}
* when invoking an API that is not available on the running broker version. * when invoking an API that is not available on the running broker version.