This is an automated email from the ASF dual-hosted git repository.
junma 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 cd4eb719a94 fix Non-persistent messaging cookbook url 404 error (#434)
cd4eb719a94 is described below
commit cd4eb719a9489729f47e4aac5d9eb8f26f833cda
Author: sunheyi <[email protected]>
AuthorDate: Fri Feb 24 22:17:23 2023 +0800
fix Non-persistent messaging cookbook url 404 error (#434)
---
versioned_docs/version-2.11.x/concepts-messaging.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/versioned_docs/version-2.11.x/concepts-messaging.md
b/versioned_docs/version-2.11.x/concepts-messaging.md
index 1d549b79c79..0a3f2f366d6 100644
--- a/versioned_docs/version-2.11.x/concepts-messaging.md
+++ b/versioned_docs/version-2.11.x/concepts-messaging.md
@@ -979,7 +979,7 @@ Non-persistent topics have names of this form (note the
`non-persistent` in the
non-persistent://tenant/namespace/topic
```
-For more info on using non-persistent topics, see the [Non-persistent
messaging cookbook](cookbooks-non-persistent).
+For more info on using non-persistent topics, see the [Non-persistent
messaging cookbook](cookbooks-non-persistent.md).
In non-persistent topics, brokers immediately deliver messages to all
connected subscribers *without persisting them* in
[BookKeeper](concepts-architecture-overview.md#persistent-storage). If a
subscriber is disconnected, the broker will not be able to deliver those
in-transit messages, and subscribers will never be able to receive those
messages again. Eliminating the persistent storage step makes messaging on
non-persistent topics slightly faster than on persistent topics in some cases
[...]
