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


The following commit(s) were added to refs/heads/main by this push:
     new f158504  CAMEL-16993: included recent changes on camel-kafka to the 
migration guide
f158504 is described below

commit f158504b0c08b77729d07274dfa103296034316c
Author: Otavio Rodolfo Piske <[email protected]>
AuthorDate: Wed Sep 22 11:37:35 2021 +0200

    CAMEL-16993: included recent changes on camel-kafka to the migration guide
---
 .../modules/ROOT/pages/camel-3x-upgrade-guide-3_12.adoc            | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git 
a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_12.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_12.adoc
index e154d3a..4169181 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_12.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_12.adoc
@@ -65,6 +65,11 @@ which used to be query parameter.
 Kamelet parameters that are named such as `host`, `port` are now always used 
with their configured value.
 Before the value in use may be from an ENV variable with the same name.
 
+=== camel-kafka
+
+The `camel-kafka` component was refactored to avoid blocking API calls in the 
Kafka consumer. As part of the refactoring the configuration `consumerStreams` 
was removed. In previous versions this setting configured the size thread pool 
used by the component to create Kafka consumers. As of 3.12, the size of the 
thread pool is set to be the same as the number of concurrent consumers (set by 
`consumersCount`).
+
+
 === camel-spark
 
 The `camel-spark` component has been upgraded from Spark 2.x to 3.x.
@@ -77,4 +82,4 @@ Both of the options are false by default. So, you'll need to 
set both to true if
 
 === camel-huawei
 
-All Huawei Cloud components use AK/SK as security keys to authenticate against 
the hauwei cloud backend services. Initally AK was mapped to authenticationKey 
in the endpoint class. To be in-line with Huawei Cloud's naming conventions, we 
have renamed this option from `authenticationKey` to `accessKey` for all 
components. This is a breaking change for users who are already using huawei 
cloud components until version 3.11.x. 
\ No newline at end of file
+All Huawei Cloud components use AK/SK as security keys to authenticate against 
the hauwei cloud backend services. Initally AK was mapped to authenticationKey 
in the endpoint class. To be in-line with Huawei Cloud's naming conventions, we 
have renamed this option from `authenticationKey` to `accessKey` for all 
components. This is a breaking change for users who are already using huawei 
cloud components until version 3.11.x. 

Reply via email to