Hi all, We've identified a compatibility issue between the latest versions of pulsar-client (3.0.13, 4.0.6) and older brokers that do not include PIP-344 (versions before 3.0.6). This breaks the client-side auto partitions update mechanism. To mitigate, users can upgrade the broker to version that includes PIP-344. Alternatively, user can downgrade the client to version 3.0.12 or 4.0.5.
``` 20:28:25.218 [pulsar-client-lookup-27-1] ERROR org.apache.pulsar.client.impl.PartitionedProducerImpl - \ [persistent://public/default/test-250926] Auto getting partitions failed java.util.concurrent.CompletionException: org.apache.pulsar.client.api.PulsarClientException$FeatureNotSupportedException: \ The feature of getting partitions without auto-creation is not supported by the broker. Please upgrade the broker to version that supports PIP-344 to resolve this issue. ``` Scope: * Affected clients (LTS): 3.0.13, 4.0.6; in progress: 3.0.14, 4.0.7 * Affected brokers: versions without PIP-344 (versions before 3.0.6, e.g. 2.10.*, 2.11.*) Is it expected behavior change in PIP-344? Is there any other way to mitigate this issue? References: - PIP-344 https://github.com/apache/pulsar/blob/master/pip/pip-344.md - https://github.com/apache/pulsar/pull/24554#issuecomment-3338482624 Regards, Yike
