Critical Description
Kafka Connect connectors and tasks fail when they run into an unexpected situation or error, but the framework should provide more general "bad data handling" options, including (perhaps among others):
- fail fast, which is what we do today (assuming connector actually fails and doesn't eat errors)
- retry (possibly with configs to limit)
- drop data and move on
- dead letter queue
This needs to be addressed in a way that handles errors from:
- The connector itself (e.g. connectivity issues to the other system)
- Converters/serializers (bad data, unexpected format, etc)
- SMTs
- Ideally the framework as well, though we obviously want to fix known bugs anyway
Attachments
Issue Links
- links to
- mentioned in
-
Page Loading...