This is an automated email from the ASF dual-hosted git repository.
fanningpj pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-pekko-projection.git
The following commit(s) were added to refs/heads/main by this push:
new f2487b7 fix grammar in docs (#100)
f2487b7 is described below
commit f2487b763fd19c589e274b2c74e552fd743da941
Author: PJ Fanning <[email protected]>
AuthorDate: Tue Jan 30 09:49:38 2024 +0100
fix grammar in docs (#100)
---
docs/src/main/paradox/kafka.md | 4 ++--
docs/src/main/paradox/running.md | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/src/main/paradox/kafka.md b/docs/src/main/paradox/kafka.md
index f2268c1..16305ce 100644
--- a/docs/src/main/paradox/kafka.md
+++ b/docs/src/main/paradox/kafka.md
@@ -1,4 +1,4 @@
-# Messages from and to Kafka
+# Messages from and to Apache Kafka
A typical source for Projections is messages from Kafka. Apache Pekko
Projections supports integration with Kafka using [Pekko Connectors
Kafka](https://pekko.apache.org/docs/pekko-connectors-kafka/current/).
@@ -132,7 +132,7 @@ Java
Alternatively, we can define the same projection using
@apidoc[Producer.flowWithContext](Producer$) in combination with
`atLeastOnceFlow`.
-The `WordSource` emits `WordEnvelope`s, therefore we will build a flow that
takes every single emitted `WordEnvelope` and map it into an Pekko Connectors
Kafka @apidoc[ProducerMessage$]. The `ProducerMessage` factory methods can be
used to produce a single message, multiple messages, or pass through a message
(skip a message from being produced). The @apidoc[ProducerMessage$] will pass
through @apidoc[Producer.flowWithContext](Producer$) that will publish it to
the Kafka Topic and finall [...]
+The `WordSource` emits `WordEnvelope`s, therefore we will build a flow that
takes every single emitted `WordEnvelope` and map it into an Apache Pekko
Connectors Kafka @apidoc[ProducerMessage$]. The `ProducerMessage` factory
methods can be used to produce a single message, multiple messages, or pass
through a message (skip a message from being produced). The
@apidoc[ProducerMessage$] will pass through
@apidoc[Producer.flowWithContext](Producer$) that will publish it to the Kafka
Topic and [...]
Scala
: @@snip
[KafkaDocExample.scala](/examples/src/test/scala/docs/kafka/KafkaDocExample.scala)
{ #imports-producer #producerFlow }
diff --git a/docs/src/main/paradox/running.md b/docs/src/main/paradox/running.md
index 0b3812b..2e7f82e 100644
--- a/docs/src/main/paradox/running.md
+++ b/docs/src/main/paradox/running.md
@@ -20,7 +20,7 @@ For more information on using Apache Pekko Cluster consult
Pekko's reference doc
The Sharded Daemon Process can be used to distribute `n` instances of a given
Projection across the cluster. Therefore, it's important that each Projection
instance consumes a subset of the stream of envelopes.
-How the subset is created depends on the kind of source we consume. If it's an
Pekko Connectors Kafka source, this is done by Kafka consumer groups. When
consuming from Apache Pekko Persistence Journal, the events must be sliced by
tagging them as demonstrated in the example below.
+How the subset is created depends on the kind of source we consume. If it's an
Apache Pekko Connectors Kafka source, this is done by Kafka consumer groups.
When consuming from Apache Pekko Persistence Journal, the events must be sliced
by tagging them as demonstrated in the example below.
### Tagging Events in EventSourcedBehavior
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
