This is an automated email from the ASF dual-hosted git repository.
hepin pushed a commit to branch 1.3.x
in repository https://gitbox.apache.org/repos/asf/pekko.git
The following commit(s) were added to refs/heads/1.3.x by this push:
new 3a1fbb45f7 Fix markdown links in distributed pub-sub documentation
(#2298) (#2301)
3a1fbb45f7 is described below
commit 3a1fbb45f76bcfd68a76491ca7aee925d50eb82f
Author: PJ Fanning <[email protected]>
AuthorDate: Thu Oct 9 19:15:18 2025 +0100
Fix markdown links in distributed pub-sub documentation (#2298) (#2301)
---
docs/src/main/paradox/typed/distributed-pub-sub.md | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/docs/src/main/paradox/typed/distributed-pub-sub.md
b/docs/src/main/paradox/typed/distributed-pub-sub.md
index 551f65f423..fc6bd5f2fc 100644
--- a/docs/src/main/paradox/typed/distributed-pub-sub.md
+++ b/docs/src/main/paradox/typed/distributed-pub-sub.md
@@ -26,26 +26,26 @@ The identity of the topic is a tuple of the type of
messages that can be publish
to not define multiple topics with different types and the same topic name.
Scala
-: @@snip
[PubSubExample.scala](/(/actor-typed-tests/src/test/scala/docs/org/apache/pekko/typed/pubsub/PubSubExample.scala)
{ #start-topic }
+: @@snip
[PubSubExample.scala](/actor-typed-tests/src/test/scala/docs/org/apache/pekko/typed/pubsub/PubSubExample.scala)
{ #start-topic }
Java
-: @@snip
[PubSubExample.java](/(/actor-typed-tests/src/test/java/jdocs/org/apache/pekko/typed/pubsub/PubSubExample.java)
{ #start-topic }
+: @@snip
[PubSubExample.java](/actor-typed-tests/src/test/java/jdocs/org/apache/pekko/typed/pubsub/PubSubExample.java)
{ #start-topic }
Local actors can then subscribe to the topic (and unsubscribe from it):
Scala
-: @@snip
[PubSubExample.scala](/(/actor-typed-tests/src/test/scala/docs/org/apache/pekko/typed/pubsub/PubSubExample.scala)
{ #subscribe }
+: @@snip
[PubSubExample.scala](/actor-typed-tests/src/test/scala/docs/org/apache/pekko/typed/pubsub/PubSubExample.scala)
{ #subscribe }
Java
-: @@snip
[PubSubExample.java](/(/actor-typed-tests/src/test/java/jdocs/org/apache/pekko/typed/pubsub/PubSubExample.java)
{ #subscribe }
+: @@snip
[PubSubExample.java](/actor-typed-tests/src/test/java/jdocs/org/apache/pekko/typed/pubsub/PubSubExample.java)
{ #subscribe }
And publish messages to the topic:
Scala
-: @@snip
[PubSubExample.scala](/(/actor-typed-tests/src/test/scala/docs/org/apache/pekko/typed/pubsub/PubSubExample.scala)
{ #publish }
+: @@snip
[PubSubExample.scala](/actor-typed-tests/src/test/scala/docs/org/apache/pekko/typed/pubsub/PubSubExample.scala)
{ #publish }
Java
-: @@snip
[PubSubExample.java](/(/actor-typed-tests/src/test/java/jdocs/org/apache/pekko/typed/pubsub/PubSubExample.java)
{ #publish }
+: @@snip
[PubSubExample.java](/actor-typed-tests/src/test/java/jdocs/org/apache/pekko/typed/pubsub/PubSubExample.java)
{ #publish }
## Pub Sub Scalability
@@ -64,6 +64,6 @@ for the topic will not be sent to it.
As in @ref:[Message Delivery
Reliability](../general/message-delivery-reliability.md) of Pekko, message
delivery guarantee in distributed pub sub modes is **at-most-once delivery**.
In other words, messages can be lost over the wire. In addition to that the
registry of nodes which have subscribers is eventually consistent
meaning that subscribing an actor on one node will have a short delay before
it is known on other nodes and published to.
-If you are looking for at-least-once delivery guarantee, we recommend [Pekko
Connector Kafka]($pekko.doc.dns$/docs/alp(/kafka/current/).
+If you are looking for at-least-once delivery guarantee, we recommend [Pekko
Connector Kafka]($pekko.doc.dns$/docs/pekko-connectors-kafka/current/).
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
