You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by ti...@apache.org on 2023/04/10 04:38:29 UTC
[pulsar-site] branch main updated: [fix] typo omissions concepts-messaging.md (#508)
This is an automated email from the ASF dual-hosted git repository.
tison pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
The following commit(s) were added to refs/heads/main by this push:
new f3e40ca832a [fix] typo omissions concepts-messaging.md (#508)
f3e40ca832a is described below
commit f3e40ca832a6bbd3379979f2f4a7e7eb45525f0d
Author: Mark Cola <ma...@doomsdaytuna.com>
AuthorDate: Mon Apr 10 14:38:24 2023 +1000
[fix] typo omissions concepts-messaging.md (#508)
---
docs/concepts-messaging.md | 4 ++--
versioned_docs/version-2.11.x/concepts-messaging.md | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/concepts-messaging.md b/docs/concepts-messaging.md
index 0047f4cf5ef..e86923c5a03 100644
--- a/docs/concepts-messaging.md
+++ b/docs/concepts-messaging.md
@@ -16,7 +16,7 @@ Pulsar is built on the [publish-subscribe](https://en.wikipedia.org/wiki/Publish
When a subscription is created, Pulsar [retains](concepts-architecture-overview.md#persistent-storage) all messages, even if the consumer is disconnected. The retained messages are discarded only when a consumer acknowledges that all these messages are processed successfully.
-If the consumption of a message fails and you want this message to be consumed again, you can enable [message redelivery mechanism](#message-redelivery) to request the broker to resend this message.
+If the consumption of a message fails and you want this message to be consumed again, you can enable the [message redelivery mechanism](#message-redelivery) to request the broker to resend this message.
## Messages
@@ -35,7 +35,7 @@ Messages are the basic "unit" of Pulsar. The following table lists the component
| Publish time | The timestamp of when the message is published. The timestamp is automatically applied by the producer. |
| Event time | An optional timestamp attached to a message by applications. For example, applications attach a timestamp on when the message is processed. If nothing is set to event time, the value is `0`. |
-The default size of a message is 5 MB. You can configure the max size of a message with the following configurations.
+The default max size of a message is 5 MB. You can configure the max size of a message with the following configuration options.
- In the `broker.conf` file.
diff --git a/versioned_docs/version-2.11.x/concepts-messaging.md b/versioned_docs/version-2.11.x/concepts-messaging.md
index 0c1d2037978..0816050992a 100644
--- a/versioned_docs/version-2.11.x/concepts-messaging.md
+++ b/versioned_docs/version-2.11.x/concepts-messaging.md
@@ -16,7 +16,7 @@ Pulsar is built on the [publish-subscribe](https://en.wikipedia.org/wiki/Publish
When a subscription is created, Pulsar [retains](concepts-architecture-overview.md#persistent-storage) all messages, even if the consumer is disconnected. The retained messages are discarded only when a consumer acknowledges that all these messages are processed successfully.
-If the consumption of a message fails and you want this message to be consumed again, you can enable [message redelivery mechanism](#message-redelivery) to request the broker to resend this message.
+If the consumption of a message fails and you want this message to be consumed again, you can enable the [message redelivery mechanism](#message-redelivery) to request the broker to resend this message.
## Messages
@@ -35,7 +35,7 @@ Messages are the basic "unit" of Pulsar. The following table lists the component
| Publish time | The timestamp of when the message is published. The timestamp is automatically applied by the producer. |
| Event time | An optional timestamp attached to a message by applications. For example, applications attach a timestamp on when the message is processed. If nothing is set to event time, the value is `0`. |
-The default size of a message is 5 MB. You can configure the max size of a message with the following configurations.
+The default max size of a message is 5 MB. You can configure the max size of a message with the following configuration options.
- In the `broker.conf` file.