(camel) branch camel-3.x updated: Regen for commit 1cf3d0b500c6608665875e89f9b619774e520fdd (#12014)

[davsclaus]

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

davsclaus pushed a commit to branch camel-3.x
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/camel-3.x by this push:
     new 7eea9ccdbfc Regen for commit 1cf3d0b500c6608665875e89f9b619774e520fdd 
(#12014)
7eea9ccdbfc is described below

commit 7eea9ccdbfc27410156e46929f409478e0cc3ed8
Author: github-actions[bot] 
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Thu Nov 16 12:11:18 2023 +0100

    Regen for commit 1cf3d0b500c6608665875e89f9b619774e520fdd (#12014)
    
    Signed-off-by: GitHub <nore...@github.com>
    Co-authored-by: oscerd <osc...@users.noreply.github.com>
---
 .../endpoint/dsl/KafkaEndpointBuilderFactory.java  | 32 ++++++++++++++--------
 1 file changed, 20 insertions(+), 12 deletions(-)

diff --git 
a/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/KafkaEndpointBuilderFactory.java
 
b/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/KafkaEndpointBuilderFactory.java
index b717e3ba9a5..a7a3a607159 100644
--- 
a/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/KafkaEndpointBuilderFactory.java
+++ 
b/dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/KafkaEndpointBuilderFactory.java
@@ -372,12 +372,16 @@ public interface KafkaEndpointBuilderFactory {
          * This options controls what happens when a consumer is processing an
          * exchange and it fails. If the option is false then the consumer
          * continues to the next message and processes it. If the option is 
true
-         * then the consumer breaks out, and will seek back to offset of the
-         * message that caused a failure, and then re-attempt to process this
-         * message. However this can lead to endless processing of the same
-         * message if its bound to fail every time, eg a poison message.
-         * Therefore its recommended to deal with that for example by using
-         * Camel's error handler.
+         * then the consumer breaks out. Using the default NoopCommitManager
+         * will cause the consumer to not commit the offset so that the message
+         * is re-attempted. The consumer should use the KafkaManualCommit to
+         * determine the best way to handle the message. Using either the
+         * SynchCommitManager or the AsynchCommitManager the consumer will seek
+         * back to the offset of the message that caused a failure, and then
+         * re-attempt to process this message. However this can lead to endless
+         * processing of the same message if its bound to fail every time, eg a
+         * poison message. Therefore its recommended to deal with that for
+         * example by using Camel's error handler.
          * 
          * The option is a: &lt;code&gt;boolean&lt;/code&gt; type.
          * 
@@ -396,12 +400,16 @@ public interface KafkaEndpointBuilderFactory {
          * This options controls what happens when a consumer is processing an
          * exchange and it fails. If the option is false then the consumer
          * continues to the next message and processes it. If the option is 
true
-         * then the consumer breaks out, and will seek back to offset of the
-         * message that caused a failure, and then re-attempt to process this
-         * message. However this can lead to endless processing of the same
-         * message if its bound to fail every time, eg a poison message.
-         * Therefore its recommended to deal with that for example by using
-         * Camel's error handler.
+         * then the consumer breaks out. Using the default NoopCommitManager
+         * will cause the consumer to not commit the offset so that the message
+         * is re-attempted. The consumer should use the KafkaManualCommit to
+         * determine the best way to handle the message. Using either the
+         * SynchCommitManager or the AsynchCommitManager the consumer will seek
+         * back to the offset of the message that caused a failure, and then
+         * re-attempt to process this message. However this can lead to endless
+         * processing of the same message if its bound to fail every time, eg a
+         * poison message. Therefore its recommended to deal with that for
+         * example by using Camel's error handler.
          * 
          * The option will be converted to a &lt;code&gt;boolean&lt;/code&gt;
          * type.