From efcf7c27b3f0fa5dc0252ce46f54b28a897e08bd Mon Sep 17 00:00:00 2001
From: Wenzhi Feng <52550727+thetumbled@users.noreply.github.com>
Date: Wed, 26 Feb 2025 15:41:27 +0800
Subject: [PATCH] [fix][doc] fix doc related to chunk message feature. (#24023)

---
 .../java/org/apache/pulsar/client/api/ProducerBuilder.java | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/pulsar-client-api/src/main/java/org/apache/pulsar/client/api/ProducerBuilder.java b/pulsar-client-api/src/main/java/org/apache/pulsar/client/api/ProducerBuilder.java
index 896c22313247a..6015bc7af2174 100644
--- a/pulsar-client-api/src/main/java/org/apache/pulsar/client/api/ProducerBuilder.java
+++ b/pulsar-client-api/src/main/java/org/apache/pulsar/client/api/ProducerBuilder.java
@@ -328,12 +328,11 @@ public interface ProducerBuilder<T> extends Cloneable {
      * of the pulsar producer and consumer is recommended to use this feature:
      *
      * <pre>
-     * 1. This feature is currently only supported for non-shared subscriptions and persistent topics.
-     * 2. Disable batching to use chunking feature.
-     * 3. Pulsar-client stores published messages in buffer cache until it receives acknowledgement from the broker.
+     * 1. Disable batching to use chunking feature.
+     * 2. Pulsar-client stores published messages in buffer cache until it receives acknowledgement from the broker.
      * Therefore, it's best practice to reduce the "maxPendingMessages" size to avoid the producer occupying large
      * amounts of memory with buffered messages.
-     * 4. Set message-ttl on the namespace to clean up incomplete chunked messages.
+     * 3. Set message-ttl on the namespace to clean up incomplete chunked messages.
      * (If a producer fails to publish an entire large message, the consumer will be unable to consume and acknowledge
      * those messages. These messages can only be discarded by message TTL or by configuring
      * {@link ConsumerBuilder#expireTimeOfIncompleteChunkedMessage}.