This is an automated email from the ASF dual-hosted git repository.
orpiske pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 8ee003d3970fafea966a61960e1eee7fe35e51e2
Author: Otavio Rodolfo Piske <angusyo...@gmail.com>
AuthorDate: Thu Aug 1 16:58:21 2024 +0200
CAMEL-21040: fix documentation in camel-google-pubsub-lite
---
.../src/main/docs/google-pubsub-lite-component.adoc | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git
a/components/camel-google/camel-google-pubsub-lite/src/main/docs/google-pubsub-lite-component.adoc
b/components/camel-google/camel-google-pubsub-lite/src/main/docs/google-pubsub-lite-component.adoc
index 81b85ee8a1c..3a56119a7d6 100644
---
a/components/camel-google/camel-google-pubsub-lite/src/main/docs/google-pubsub-lite-component.adoc
+++
b/components/camel-google/camel-google-pubsub-lite/src/main/docs/google-pubsub-lite-component.adoc
@@ -68,15 +68,17 @@ include::partial$component-endpoint-headers.adoc[]
== Producer Endpoints
-Google PubSub Lite expects the payload to be byte[] array, Producer endpoints
will send:
+Google PubSub Lite expects the payload to be `byte[]` array, Producer
endpoints will send:
-* String body as byte[] encoded as UTF-8
-* byte[] body as is
-* Everything else will be serialised into byte[] array
+* String body as `byte[]` encoded as UTF-8
+* `byte[]` body as is
+* Everything else will be serialised into a `byte[]` array
A Map set as message header `GooglePubsubConstants.ATTRIBUTES` will be sent as
PubSub attributes.
-When producing messages set the message header
`GooglePubsubConstants.ORDERING_KEY` . This will be set as the PubSub Lite
orderingKey for the message. More information in
https://cloud.google.com/pubsub/lite/docs/publishing#using_ordering_keys[Using
ordering keys].
+When producing messages set the message header
`GooglePubsubConstants.ORDERING_KEY`.
+This will be set as the PubSub Lite orderingKey for the message.
+You can find more information on
https://cloud.google.com/pubsub/lite/docs/publishing#using_ordering_keys[Using
ordering keys].
== Consumer Endpoints
@@ -86,7 +88,7 @@ The component will acknowledge the message once exchange
processing has been com
== Message Body
-The consumer endpoint returns the content of the message as byte[] - exactly
as the underlying system sends it.
+The consumer endpoint returns the content of the message as `byte[]` - exactly
as the underlying system sends it.
It is up for the route to convert/unmarshall the contents.
== Examples
