This is an automated email from the ASF dual-hosted git repository.
zregvart pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-kafka-connector.git
The following commit(s) were added to refs/heads/master by this push:
new 64eb4c7 fix: xref typo
64eb4c7 is described below
commit 64eb4c78afe1e9c7056d189b95a90d49c811c6f7
Author: Zoran Regvart <zregv...@apache.org>
AuthorDate: Wed Nov 4 22:16:52 2020 +0100
fix: xref typo
---
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 d1b4aca..54a4986 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:
