Error handling 1st part #653
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #407
This is just a beginning: we have two strategies for error handling at Camel level, "no" and "default", the first won't do anything, the second will do just like the defaultErrorHandler, but we have now the option to set the number of redelivery and redelivery delay.
In ckc we'll have to deal with two-level error handling: the Camel level and Kafka connect level. While the kc stuff is more or less already built-in with the kc options, for Camel we may need to find a way to specify a list of possible exceptions and inject them through the configuration.
I don't believe we need a transactionalErrorHandler in ckc.