This is an automated email from the ASF dual-hosted git repository.
penghui pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new 8b46d59 [Documentation] Fix typo: maxPendingChuckedMessage should be
maxPendingChunkedMessage (#10253)
8b46d59 is described below
commit 8b46d59f29d2487f938dca8b1e1a7770e49bec02
Author: Michael Marshall <[email protected]>
AuthorDate: Mon Apr 19 08:31:29 2021 -0600
[Documentation] Fix typo: maxPendingChuckedMessage should be
maxPendingChunkedMessage (#10253)
In https://github.com/apache/pulsar/pull/10223, I fixed many references to
`chuck` that should have been `chunk`. I missed one documentation reference.
This PR fixes that.
(Note that the old 2.6.x and 2.7.x documentation still reference `chuck`
because that is what the java client's API uses. Moving forward, we will use
`chunk`, as https://github.com/apache/pulsar/pull/10223 demonstrates.)
---
site2/docs/concepts-messaging.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/site2/docs/concepts-messaging.md b/site2/docs/concepts-messaging.md
index 28f7ac5..32ea4f8 100644
--- a/site2/docs/concepts-messaging.md
+++ b/site2/docs/concepts-messaging.md
@@ -101,7 +101,7 @@ When you enable chunking, read the following instructions.
When chunking is enabled (`chunkingEnabled=true`), if the message size is
greater than the allowed maximum publish-payload size, the producer splits the
original message into chunked messages and publishes them with chunked metadata
to the broker separately and in order. At the broker side, the chunked messages
are stored in the managed-ledger in the same way as that of ordinary messages.
The only difference is that the consumer needs to buffer the chunked messages
and combines them into [...]
-The consumer consumes the chunked messages and buffers them until the consumer
receives all the chunks of a message. And then the consumer stitches chunked
messages together and places them into the receiver-queue. Clients consume
messages from the receiver-queue. Once the consumer consumes the entire large
message and acknowledges it, the consumer internally sends acknowledgement of
all the chunk messages associated to that large message. You can set the
`maxPendingChuckedMessage` param [...]
+The consumer consumes the chunked messages and buffers them until the consumer
receives all the chunks of a message. And then the consumer stitches chunked
messages together and places them into the receiver-queue. Clients consume
messages from the receiver-queue. Once the consumer consumes the entire large
message and acknowledges it, the consumer internally sends acknowledgement of
all the chunk messages associated to that large message. You can set the
`maxPendingChunkedMessage` param [...]
The broker does not require any changes to support chunking for non-shared
subscription. The broker only uses `chunkedMessageRate` to record chunked
message rate on the topic.
