This is an automated email from the ASF dual-hosted git repository.
zregvart pushed a commit to branch camel-kafka-connector-0.4.x
in repository https://gitbox.apache.org/repos/asf/camel-kafka-connector.git
The following commit(s) were added to refs/heads/camel-kafka-connector-0.4.x by
this push:
new 67b1451 fix: xref typo
67b1451 is described below
commit 67b1451d21e587adc7c943bc94482e0e9855aa4f
Author: Zoran Regvart <[email protected]>
AuthorDate: Wed Nov 4 22:16:52 2020 +0100
fix: xref typo
(cherry picked from commit 64eb4c78afe1e9c7056d189b95a90d49c811c6f7)
---
docs/modules/ROOT/pages/aggregation.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/modules/ROOT/pages/aggregation.adoc
b/docs/modules/ROOT/pages/aggregation.adoc
index fc33ed1..ad469eb 100644
--- a/docs/modules/ROOT/pages/aggregation.adoc
+++ b/docs/modules/ROOT/pages/aggregation.adoc
@@ -4,7 +4,7 @@
In a Sink Connector scenario, there are, sometimes, use cases where an end
user want to aggregate his Kafka record before sending them to an external
system.
Usually this can be done by defining a batch size or a timeout and once the
aggregation has been completed, sent the aggregate records collection to the
external system.
-In Apache Camel it exists the
xref:latest@components:eips/aggregate-eip.adoc[Aggregate EIP] implementation
and in Camel-Kafka-connector we wanted to leverage what we already have in the
plain Apache Camel project.
+In Apache Camel it exists the
xref:latest@components:eips:aggregate-eip.adoc[Aggregate EIP] implementation
and in Camel-Kafka-connector we wanted to leverage what we already have in the
plain Apache Camel project.
We introduced then the following options in the Sink Connector Configuration:
