Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for dead-letter queue and ignoring bad messages #721

rmoff opened this issue Oct 15, 2019 · 1 comment


Copy link

@rmoff rmoff commented Oct 15, 2019

It would be useful if the JDBC sink connector had better support for when messages are read that cannot be written to the target database. This includes errors such as missing mandatory fields, wrong data types, data lengths exceeding the target column size, key violations, etc.

At the moment the connector will abort and the user has to somehow fix the pipeline.

It would be useful to add:

  • Dead-letter queue : records that cannot be written to the target RDBMS are skipped and routed to a specified Kafka topic instead
  • Ignore failing records : similar to how the Elasticsearch sink has behavior.on.malformed.documents, JDBC sink connector should also do the same.
@rmoff rmoff added the enhancement label Oct 15, 2019

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.