Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-6738

Kafka Connect handling of bad data

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 1.1.0
    • Fix Version/s: 2.0.0
    • Component/s: KafkaConnect
    • Labels:
      None

      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):

      1. fail fast, which is what we do today (assuming connector actually fails and doesn't eat errors)
      2. retry (possibly with configs to limit)
      3. drop data and move on
      4. dead letter queue

      This needs to be addressed in a way that handles errors from:

      1. The connector itself (e.g. connectivity issues to the other system)
      2. Converters/serializers (bad data, unexpected format, etc)
      3. SMTs
      4. Ideally the framework as well, though we obviously want to fix known bugs anyway

        Attachments

          Activity

            People

            • Assignee:
              wicknicks Arjun Satish
              Reporter:
              rhauch Randall Hauch
              Reviewer:
              Ewen Cheslack-Postava
            • Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: