You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by or...@apache.org on 2024/02/21 15:29:38 UTC
(camel) branch main updated (69ab31605ba -> aea7cb03c34)
This is an automated email from the ASF dual-hosted git repository.
orpiske pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
from 69ab31605ba camel-cloudevents - Add 1.0.2 spec
new 66e47fbee29 CAMEL-20410: documentation fixes for camel-parquet-avro
new 24b804eef3c CAMEL-20410: documentation fixes for camel-pdf
new 577b7a9b23c CAMEL-20410: documentation fixes for camel-pg-replication-slot
new 13e8b2da58f CAMEL-20410: documentation fixes for camel-pgevent
new c92c7652dd1 CAMEL-20410: documentation fixes for camel-plc4x
new 2daf2b0d22d CAMEL-20410: documentation fixes for camel-printer
new dcae4ed0a61 CAMEL-20410: documentation fixes for camel-protobuf
new b4bec897f3e CAMEL-20410: documentation fixes for camel-pubnub
new aea7cb03c34 CAMEL-20410: documentation fixes for camel-python
The 9 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../src/main/docs/parquetAvro-dataformat.adoc | 13 +++++-----
.../camel-pdf/src/main/docs/pdf-component.adoc | 6 ++---
.../main/docs/pg-replication-slot-component.adoc | 10 ++++----
.../src/main/docs/pgevent-component.adoc | 2 +-
.../camel-plc4x/src/main/docs/plc4x-component.adoc | 7 +++---
.../camel-printer/src/main/docs/lpr-component.adoc | 18 +++++++-------
.../src/main/docs/protobuf-dataformat.adoc | 22 +++++++++--------
.../src/main/docs/pubnub-component.adoc | 28 ++++++++++++----------
.../src/main/docs/python-language.adoc | 9 ++++---
9 files changed, 60 insertions(+), 55 deletions(-)
(camel) 06/09: CAMEL-20410: documentation fixes for camel-printer
Posted by or...@apache.org.
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 2daf2b0d22d916efa0e2f2d16b9a95531e8cf969
Author: Otavio Rodolfo Piske <an...@gmail.com>
AuthorDate: Wed Feb 21 15:56:02 2024 +0100
CAMEL-20410: documentation fixes for camel-printer
- Fixed samples
- Fixed grammar and typos
- Fixed punctuation
- Added and/or fixed links
- Converted to use tabs
---
.../camel-printer/src/main/docs/lpr-component.adoc | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/components/camel-printer/src/main/docs/lpr-component.adoc b/components/camel-printer/src/main/docs/lpr-component.adoc
index 3a44253c447..064af213f2f 100644
--- a/components/camel-printer/src/main/docs/lpr-component.adoc
+++ b/components/camel-printer/src/main/docs/lpr-component.adoc
@@ -15,8 +15,8 @@
*{component-header}*
The Printer component provides a way to direct payloads on a route to
-a printer. Obviously the payload has to be a formatted piece of payload
-in order for the component to appropriately print it. The objective is
+a printer. The payload has to be a formatted piece of payload
+in order for the component to appropriately print it. The goal is
to be able to direct specific payloads as jobs to a line printer in a
camel flow.
@@ -40,7 +40,7 @@ for this component:
== URI format
Since the URI scheme for a printer has not been standardized (the
-nearest thing to a standard being the IETF print standard) and therefore
+nearest thing to a standard being the IETF print standard), and therefore
not uniformly applied by vendors, we have chosen *"lpr"* as the scheme.
-----------------------------------------------
@@ -74,7 +74,7 @@ route.
== Usage Samples
-=== Example 1: Printing text based payloads on a Default printer using letter stationary and one-sided mode
+=== Example 1: Printing text-based payloads on a Default printer using letter stationary and one-sided mode
[source,java]
-----------------------------------------------
@@ -85,11 +85,11 @@ RouteBuilder builder = new RouteBuilder() {
"&flavor=DocFlavor.INPUT_STREAM&" +
"&mimeType=AUTOSENSE" +
"&mediaSize=NA_LETTER" +
- "&sides=one-sided")
+ "&sides=one-sided");
}};
-----------------------------------------------
-=== Example 2: Printing GIF based payloads on a Remote printer using A4 stationary and one-sided mode
+=== Example 2: Printing GIF-based payloads on a remote printer using A4 stationary and one-sided mode
[source,java]
--------------------------------------------------
@@ -99,11 +99,11 @@ RouteBuilder builder = new RouteBuilder() {
.to("lpr://remotehost/sales/salesprinter" +
"?copies=2&sides=one-sided" +
"&mimeType=GIF&mediaSize=ISO_A4" +
- "&flavor=DocFlavor.INPUT_STREAM")
+ "&flavor=DocFlavor.INPUT_STREAM");
}};
--------------------------------------------------
-=== Example 3: Printing JPEG based payloads on a Remote printer using Japanese Postcard stationary and one-sided mode
+=== Example 3: Printing JPEG-based payloads on a remote printer using Japanese Postcard stationary and one-sided mode
[source,java]
--------------------------------------------------
@@ -114,7 +114,7 @@ RouteBuilder builder = new RouteBuilder() {
"?copies=2&sides=one-sided" +
"&mimeType=JPEG" +
"&mediaSize=JAPANESE_POSTCARD" +
- "&flavor=DocFlavor.INPUT_STREAM")
+ "&flavor=DocFlavor.INPUT_STREAM");
}};
--------------------------------------------------
(camel) 09/09: CAMEL-20410: documentation fixes for camel-python
Posted by or...@apache.org.
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 aea7cb03c341dc295275e5603e448894645e322f
Author: Otavio Rodolfo Piske <an...@gmail.com>
AuthorDate: Wed Feb 21 16:05:44 2024 +0100
CAMEL-20410: documentation fixes for camel-python
- Fixed samples
- Fixed grammar and typos
- Fixed punctuation
- Added and/or fixed links
- Converted to use tabs
---
components/camel-python/src/main/docs/python-language.adoc | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/components/camel-python/src/main/docs/python-language.adoc b/components/camel-python/src/main/docs/python-language.adoc
index 7809828a23d..efa93a748c8 100644
--- a/components/camel-python/src/main/docs/python-language.adoc
+++ b/components/camel-python/src/main/docs/python-language.adoc
@@ -16,7 +16,7 @@ used as an xref:manual::expression.adoc[Expression] or xref:manual::predicate.ad
in Camel routes.
For example, you can use Python in a xref:manual::predicate.adoc[Predicate]
-with the xref:eips:choice-eip.adoc[Content Based Router] EIP.
+with the xref:eips:choice-eip.adoc[Content-Based Router] EIP.
== Python Options
@@ -46,12 +46,11 @@ include::partial$language-options.adoc[]
== Dependencies
-To use Python in your camel routes you need to add the dependency on
+To use Python in your Camel routes, you need to add the dependency on
*camel-python* which implements the Python language.
-If you use maven you could just add the following to your pom.xml,
-substituting the version number for the latest & greatest release (see
-the download page for the latest versions).
+If you use Maven, you could add the following to your `pom.xml`,
+substituting the version number for the latest & greatest release.
[source,xml]
-------------------------------------
(camel) 04/09: CAMEL-20410: documentation fixes for camel-pgevent
Posted by or...@apache.org.
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 13e8b2da58f33e35aec70eb9795d9cd7520bd81a
Author: Otavio Rodolfo Piske <an...@gmail.com>
AuthorDate: Wed Feb 21 15:50:36 2024 +0100
CAMEL-20410: documentation fixes for camel-pgevent
- Fixed samples
- Fixed grammar and typos
- Fixed punctuation
- Added and/or fixed links
- Converted to use tabs
---
components/camel-pgevent/src/main/docs/pgevent-component.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/components/camel-pgevent/src/main/docs/pgevent-component.adoc b/components/camel-pgevent/src/main/docs/pgevent-component.adoc
index 3b9227c66bf..754912e26e5 100644
--- a/components/camel-pgevent/src/main/docs/pgevent-component.adoc
+++ b/components/camel-pgevent/src/main/docs/pgevent-component.adoc
@@ -14,7 +14,7 @@
*{component-header}*
-This is a component for Apache Camel which allows for
+This is a component for Apache Camel that allows for
Producing/Consuming PostgreSQL events related to the LISTEN/NOTIFY
commands added since PostgreSQL 8.3.
(camel) 07/09: CAMEL-20410: documentation fixes for camel-protobuf
Posted by or...@apache.org.
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 dcae4ed0a61e8f23e9ba3db9d1feff18754e2482
Author: Otavio Rodolfo Piske <an...@gmail.com>
AuthorDate: Wed Feb 21 15:59:14 2024 +0100
CAMEL-20410: documentation fixes for camel-protobuf
- Fixed samples
- Fixed grammar and typos
- Fixed punctuation
- Added and/or fixed links
- Converted to use tabs
---
.../src/main/docs/protobuf-dataformat.adoc | 22 ++++++++++++----------
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git a/components/camel-protobuf/src/main/docs/protobuf-dataformat.adoc b/components/camel-protobuf/src/main/docs/protobuf-dataformat.adoc
index dbe1848cad7..863da26be3f 100644
--- a/components/camel-protobuf/src/main/docs/protobuf-dataformat.adoc
+++ b/components/camel-protobuf/src/main/docs/protobuf-dataformat.adoc
@@ -40,7 +40,7 @@ include::partial$dataformat-options.adoc[]
It's possible to parse JSON message to convert it to the protobuf format and unparse it back using native util converter.
To use this option, set contentTypeFormat value to 'json' or call protobuf with second parameter.
-If default instance is not specified, always use native protobuf format.
+If the default instance is not specified, always use the native protobuf format.
The sample code shows below:
[source,java]
@@ -52,16 +52,18 @@ from("direct:marshal")
--------------------------------------------------------------------------------------------------
== Input data type
-This dataformat supports marshaling input data either as protobuf `Message` type or `Map` data type. In case of input data as `Map` type, first it will try to retrieve the data as `Map` using built-in type converters, if it fails to
+This dataformat supports marshaling input data either as protobuf `Message` type or `Map` data type.
+In case of input data as `Map` type, first it will try to retrieve the data as `Map` using built-in type converters, if it fails to
do so, it will fall back to retrieve it as proto `Message`.
== Output data type
-As mentioned above, you can define the content type format to choose from JSON or native to serialize/deserialize data from/to. In addition, you can also obtain the data as `Map` and let this component to do the heavy lifting to parse the
-data from proto `Message` to `Map`, you will just need to set the `contentTypeFormat` to *native* and explicitly define the data type `Map` when you obtain body of the exchange, e.g: `exchange.getMessage().getBody(Map.class)`.
+As mentioned above, you can define the content type format to choose from JSON or native to serialize/deserialize data from/to.
+In addition, you can also obtain the data as `Map` and let this component do the heavy lifting to parse the
+data from proto `Message` to `Map`, you will need to set the `contentTypeFormat` to *native* and explicitly define the data type `Map` when you obtain body of the exchange, e.g.: `exchange.getMessage().getBody(Map.class)`.
== Protobuf overview
-This quick overview of how to use Protobuf. For more detail see the
+This quick overview of how to use Protobuf. For more detail, see the
https://developers.google.com/protocol-buffers/docs/javatutorial[complete tutorial]
== Defining the proto format
@@ -108,8 +110,8 @@ message AddressBook {
The Protobuf SDK provides a compiler which will generate the Java
classes for the format we defined in our .proto file.
-If your operating system is supporting by https://www.xolstice.org/protobuf-maven-plugin[Protobuf Java code generator maven plugin],
-you can automate protobuf Java code generating by adding following configurations to your pom.xml:
+If your operating system is supported by https://www.xolstice.org/protobuf-maven-plugin[Protobuf Java code generator maven plugin],
+you can automate protobuf Java code generating by adding the following configurations to your `pom.xml`:
Insert operating system and CPU architecture detection extension inside **<build>** tag of the project pom.xml or set ${os.detected.classifier} parameter manually
[source,xml]
@@ -152,7 +154,7 @@ This will generate a single Java class named AddressBookProtos which
contains inner classes for Person and AddressBook. Builders are also
implemented for you. The generated classes implement
com.google.protobuf.Message which is required by the serialization
-mechanism. For this reason it important that only these classes are used
+mechanism. For this reason it is important that only these classes are used
in the body of your exchanges. Camel will throw an exception on route
creation if you attempt to tell the Data Format
to use a class that does not implement com.google.protobuf.Message. Use
@@ -206,8 +208,8 @@ configuring the protobuf data type
== Dependencies
-To use Protobuf in your camel routes you need to add the a dependency on
-*camel-protobuf* which implements this data format.
+To use Protobuf in your Camel routes you need to add the dependency on
+*camel-protobuf*, which implements this data format.
[source,xml]
-----------------------------------------
(camel) 08/09: CAMEL-20410: documentation fixes for camel-pubnub
Posted by or...@apache.org.
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 b4bec897f3e70597abcf035529dd5ad6ca2a640f
Author: Otavio Rodolfo Piske <an...@gmail.com>
AuthorDate: Wed Feb 21 16:04:14 2024 +0100
CAMEL-20410: documentation fixes for camel-pubnub
- Fixed samples
- Fixed grammar and typos
- Fixed punctuation
- Added and/or fixed links
- Converted to use tabs
---
.../src/main/docs/pubnub-component.adoc | 28 ++++++++++++----------
1 file changed, 16 insertions(+), 12 deletions(-)
diff --git a/components/camel-pubnub/src/main/docs/pubnub-component.adoc b/components/camel-pubnub/src/main/docs/pubnub-component.adoc
index c2ab5958f95..3844f1fb407 100644
--- a/components/camel-pubnub/src/main/docs/pubnub-component.adoc
+++ b/components/camel-pubnub/src/main/docs/pubnub-component.adoc
@@ -65,18 +65,22 @@ include::partial$component-endpoint-headers.adoc[]
== Message body
-The message body can contain any JSON serializable data, including: Objects, Arrays, Ints and Strings. Message data should not contain special Java V4 classes or functions as these will not serialize. String content can include any single-byte or multi-byte UTF-8
+The message body can contain any JSON serializable data, including Objects, Arrays, Integers, and Strings.
+Message data should not contain special Java V4 classes or functions as these will not serialize.
+String content can include any single-byte or multibyte UTF-8.
-Object serialization when sending is done automatically. Just pass the full object as the message payload. PubNub will takes care of object serialization.
+Object serialization when sending is done automatically.
+Pass the full object as the message payload.
+PubNub will take care of object serialization.
-When receiving the message body utilize objects provided by the PubNub API.
+When receiving the message body uses objects provided by the PubNub API.
== Examples
=== Publishing events
Default operation when producing.
-The following snippet publish the event generated by PojoBean to the channel iot.
+The following snippet publishes the event generated by PojoBean to the channel iot.
[source,java]
----
@@ -88,7 +92,7 @@ from("timer:mytimer")
=== Fire events aka BLOCKS Event Handlers
-See https://www.pubnub.com/blocks-catalog/ for all kind of serverless functions that can be invoked.
+See https://www.pubnub.com/blocks-catalog/[blocks catalog] for all kinds of serverless functions that can be invoked.
Example of geolocation lookup
[source,java]
@@ -117,7 +121,7 @@ from("pubnub:iot?subscribeKey=mySubscribeKey")
=== Performing operations
-herenow : Obtain information about the current state of a channel including a list of unique user-ids currently subscribed to the channel and the total occupancy count of the channel
+- `herenow`: obtain information about the current state of a channel including a list of unique user-ids currently subscribed to the channel and the total occupancy count of the channel:
[source,java]
----
@@ -126,7 +130,7 @@ from("direct:control")
.to("mock:result");
----
-wherenow : Obtain information about the current list of channels to which a uuid is subscribed
+- `wherenow`: obtain information about the current list of channels to which a uuid is subscribed:
[source,java]
----
@@ -135,7 +139,7 @@ from("direct:control")
.to("mock:result");
----
-setstate : Used to set key/value pairs specific to a subscriber uuid.
+- `setstate`: used to set key/value pairs specific to a subscriber uuid:
[source,java]
----
@@ -144,7 +148,7 @@ from("direct:control")
.to("pubnub:myChannel?publishKey=mypublishKey&subscribeKey=mySubscribeKey&operation=setstate&uuid=myuuid");
----
-gethistory : Fetches historical messages of a channel.
+- `gethistory`: Fetches historical messages of a channel:
[source,java]
----
@@ -152,11 +156,11 @@ from("direct:control")
.to("pubnub:myChannel?publishKey=mypublishKey&subscribeKey=mySubscribeKey&operation=gethistory");
----
-There is a couple of examples in test directory that shows some of the PubNub features.
+There are a couple of examples in the test directory that show some of the PubNub features.
They require a PubNub account, from where you can obtain a publish- and subscribe key.
-The example PubNubSensorExample already contains a subscribe key provided by PubNub, so this is ready to run without a account.
-The example illustrates the PubNub component subscribing to a infinite stream of sensor data.
+The example PubNubSensorExample already contains a subscribe key provided by PubNub, so this is ready to run without an account.
+The example illustrates the PubNub component subscribing to an infinite stream of sensor data.
(camel) 05/09: CAMEL-20410: documentation fixes for camel-plc4x
Posted by or...@apache.org.
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 c92c7652dd1b4deef166f7c331da2066d302611e
Author: Otavio Rodolfo Piske <an...@gmail.com>
AuthorDate: Wed Feb 21 15:53:48 2024 +0100
CAMEL-20410: documentation fixes for camel-plc4x
- Fixed samples
- Fixed grammar and typos
- Fixed punctuation
- Added and/or fixed links
- Converted to use tabs
---
components/camel-plc4x/src/main/docs/plc4x-component.adoc | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/components/camel-plc4x/src/main/docs/plc4x-component.adoc b/components/camel-plc4x/src/main/docs/plc4x-component.adoc
index 8366b592a4f..2512f80f44a 100644
--- a/components/camel-plc4x/src/main/docs/plc4x-component.adoc
+++ b/components/camel-plc4x/src/main/docs/plc4x-component.adoc
@@ -24,8 +24,7 @@ plc4x://driver[?options]
The bucket will be created if it doesn't already exist.
-You can append query options to the URI in the following format,
-?options=value&option2=value&...
+You can append query options to the URI in the following format: `?options=value&option2=value&...`.
// component-configure options: START
@@ -48,7 +47,7 @@ include::partial$component-endpoint-headers.adoc[]
== Dependencies
-Maven users will need to add the following dependency to their pom.xml.
+Maven users will need to add the following dependency to their `pom.xml`.
*pom.xml*
@@ -76,7 +75,7 @@ read from the PLC.
== Polling Consumer
-The polling consumer supports consecutive reading. The input and output is the same as for the regular consumer.
+The polling consumer supports consecutive reading. The input and output are the same as for the regular consumer.
== Producer
(camel) 02/09: CAMEL-20410: documentation fixes for camel-pdf
Posted by or...@apache.org.
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 24b804eef3ca61c8779aba31a1e0226daeb91b61
Author: Otavio Rodolfo Piske <an...@gmail.com>
AuthorDate: Wed Feb 21 15:47:54 2024 +0100
CAMEL-20410: documentation fixes for camel-pdf
- Fixed samples
- Fixed grammar and typos
- Fixed punctuation
- Added and/or fixed links
- Converted to use tabs
---
components/camel-pdf/src/main/docs/pdf-component.adoc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/components/camel-pdf/src/main/docs/pdf-component.adoc b/components/camel-pdf/src/main/docs/pdf-component.adoc
index 644a1f591f1..f6e4412be53 100644
--- a/components/camel-pdf/src/main/docs/pdf-component.adoc
+++ b/components/camel-pdf/src/main/docs/pdf-component.adoc
@@ -14,12 +14,12 @@
*{component-header}*
-The PDF components provides the ability to create, modify or extract
+The PDF component provides the ability to create, modify or extract
content from PDF documents. This component uses
-https://pdfbox.apache.org/[Apache PDFBox] as underlying library to work
+https://pdfbox.apache.org/[Apache PDFBox] as the underlying library to work
with PDF documents.
-In order to use the PDF component, Maven users will need to add the
+To use the PDF component, Maven users will need to add the
following dependency to their `pom.xml`:
*pom.xml*
(camel) 01/09: CAMEL-20410: documentation fixes for camel-parquet-avro
Posted by or...@apache.org.
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 66e47fbee299b8ee0a36210d7c31ccc82e685c06
Author: Otavio Rodolfo Piske <an...@gmail.com>
AuthorDate: Wed Feb 21 15:47:08 2024 +0100
CAMEL-20410: documentation fixes for camel-parquet-avro
- Fixed samples
- Fixed grammar and typos
- Fixed punctuation
- Added and/or fixed links
- Converted to use tabs
---
.../src/main/docs/parquetAvro-dataformat.adoc | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/components/camel-parquet-avro/src/main/docs/parquetAvro-dataformat.adoc b/components/camel-parquet-avro/src/main/docs/parquetAvro-dataformat.adoc
index a719c873c14..236b6aa1dad 100644
--- a/components/camel-parquet-avro/src/main/docs/parquetAvro-dataformat.adoc
+++ b/components/camel-parquet-avro/src/main/docs/parquetAvro-dataformat.adoc
@@ -11,7 +11,9 @@
*Since Camel {since}*
-The ParquetAvro Data Format is a Camel Framework's data format implementation based on parquet-avro library for (de)/serialization purposes. Messages can be unmarshalled to Avro's GenericRecords or plain Java objects (POJOs). By the help of Camel's routing engine and data transformations you can then play with them and apply customised formatting and call other Camel Component's to convert and send messages to upstream systems.
+The ParquetAvro Data Format is a Camel Framework's data format implementation based on the parquet-avro library for (de)/serialization purposes.
+Messages can be unmarshalled to Avro's GenericRecords or plain Java objects (POJOs).
+With the help of Camel's routing engine and data transformations, you can then play with them and apply customised formatting and call other Camel Components to convert and send messages to upstream systems.
== Parquet Data Format Options
@@ -21,7 +23,7 @@ include::partial$dataformat-options.adoc[]
== Unmarshal
-There are ways to unmarshal parquet files/structures (Usually binary parquet files) where camel DSL allows
+There are ways to unmarshal parquet files/structures, usually binary parquet files, where camel DSL allows.
In this first example we unmarshal file payload to OutputStream and send it to mock endpoint, then we will be able to get GenericRecord or POJO (it could be a list if that is coming through)
@@ -32,7 +34,7 @@ from("direct:unmarshal").unmarshal(parquet).to("mock:unmarshal");
== Marshal
-Marshalling is the reverse process of unmarshalling so when you have your GenericRecord or POJO and marshal it you will get the parquet formatted output stream on your producer endpoint.
+Marshalling is the reverse process of unmarshalling, so when you have your GenericRecord or POJO and marshal it, you will get the parquet-formatted output stream on your producer endpoint.
[source,java]
-----------------------------------------------------------------------
@@ -44,9 +46,8 @@ from("direct:marshal").marshal(parquet).to("mock:marshal");
To use parquet-avro data format in your camel routes you need to add a dependency on
*camel-parquet-avro* which implements this data format.
-If you use Maven you can just add the following to your `pom.xml`,
-substituting the version number for the latest & greatest release (see
-the download page for the latest versions).
+If you use Maven you can add the following to your `pom.xml`,
+substituting the version number for the latest & greatest release.
[source,xml]
----------------------------------------------------------
(camel) 03/09: CAMEL-20410: documentation fixes for camel-pg-replication-slot
Posted by or...@apache.org.
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 577b7a9b23c576164f3cb3d4786051e716461bef
Author: Otavio Rodolfo Piske <an...@gmail.com>
AuthorDate: Wed Feb 21 15:49:47 2024 +0100
CAMEL-20410: documentation fixes for camel-pg-replication-slot
- Fixed samples
- Fixed grammar and typos
- Fixed punctuation
- Added and/or fixed links
- Converted to use tabs
---
.../src/main/docs/pg-replication-slot-component.adoc | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/components/camel-pg-replication-slot/src/main/docs/pg-replication-slot-component.adoc b/components/camel-pg-replication-slot/src/main/docs/pg-replication-slot-component.adoc
index 4f8f48e0617..bf34ce7d181 100644
--- a/components/camel-pg-replication-slot/src/main/docs/pg-replication-slot-component.adoc
+++ b/components/camel-pg-replication-slot/src/main/docs/pg-replication-slot-component.adoc
@@ -14,8 +14,8 @@
*{component-header}*
-This is a component for Apache Camel which allows for
-consuming from PostgreSQL replication slots. The component works with PostgreSQL 10 or later.
+This is a component for Apache Camel that allows consuming from PostgreSQL replication slots.
+The component works with PostgreSQL 10 or later.
Maven users will need to add the following dependency to their `pom.xml`
for this component:
@@ -62,13 +62,13 @@ from("pg-replication-slot://localhost:5432/finance/sync_slot:test_decoding?user=
== Tips
-PostgreSQL can generate a huge amount of empty transactions on certain operations (e.g. `VACUUM`). These transactions can congest
+PostgreSQL can generate a huge number of empty transactions on certain operations (e.g. `VACUUM`). These transactions can congest
your route. Using `greedy=true` query parameter can help with this problem. It will help your route filter out empty transactions quickly
without waiting for the `delay`*`timeUnit` parameter between each exchange.
The order of the messages is guaranteed, but the same message might come more than once. So, for example, if you're using
-this component to sync data from PostgreSQL to other database, make sure your operations are idempotent (e.g. use UPSERT
-instead of INSERT,...). This will make sure repeated messages won't affect your system negatively.
+this component to sync data from PostgreSQL to another database, make sure your operations are idempotent (e.g., use `UPSERT`
+instead of `INSERT`, etc). This will make sure repeated messages won't affect your system negatively.