[
https://issues.apache.org/jira/browse/CAMEL-20089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783629#comment-17783629
]
Mike Barlotta commented on CAMEL-20089:
---------------------------------------
I do think it is important for Camel to have a flag to allow a route stop
moving forward thru the messages in a partition when an error occurs (or to
keep going). This flag does that. What is interesting is that it tries to do
more than that.
One observation regarding _breakOnFirstError_ is that it does attempt to retry
the message automatically (at least once). In the current implementation there
doesn't seem to be a way to override that behavior and it seems to have created
several issues.
I propose that if _breakOnFirstError && allowManualCommit_ that Camel would do
just unsubscribe and resubscribe. This would delegate how to handle the error
(retry or no retry) to the Camel route and how the implementation commits or
doesn't commit the offset.
> camel-kafka: make breakOnFirstError more flexible
> -------------------------------------------------
>
> Key: CAMEL-20089
> URL: https://issues.apache.org/jira/browse/CAMEL-20089
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
> Reporter: Otavio Rodolfo Piske
> Assignee: Otavio Rodolfo Piske
> Priority: Major
> Fix For: 4.x
>
>
> We have a very high incidence of problems in the camel-kafka component that
> are related to the breakOnFirstError flag.
> Looking at the tickets related to this issue it seems to me that different
> uses have different expectations about how the component should behave in
> terms of polling, rolling back, and/or future processing.
> In short: this flag is leading to a lot of confusion and we should
> investigate how we can flexibilize the behavior of the Kafka component under
> those circumstances and let the users choose more freely the behavior that is
> suitable to their needs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
