You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by zr...@apache.org on 2020/11/04 23:21:38 UTC

[camel-kafka-connector] branch camel-kafka-connector-0.6.x updated: fix: xref typo

This is an automated email from the ASF dual-hosted git repository.

zregvart pushed a commit to branch camel-kafka-connector-0.6.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.6.x by this push:
     new 976797b  fix: xref typo
976797b is described below

commit 976797bc1bf2eb58fa8362f6a5ff4b335ba7f4d5
Author: Zoran Regvart <zr...@apache.org>
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 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: