[CDCSDK] DBZ: Log full exceptions instead of just message #17541
Assignees
Labels
area/cdcsdk
CDC SDK
kind/enhancement
This is an enhancement of an existing feature
priority/medium
Medium priority issue
status/awaiting-triage
Issue awaiting triage
Comments
vaibhav-yb
added
kind/enhancement
vaibhav-yb
added a commit
to yugabyte/debezium-connector-yugabytedb
that referenced
this issue
May 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jira Link: DB-6691
Description
Today, there are places in YugabyteDB connector where when we receive an
Exception e, we are logging the message by callinge.getMessage()- this causes issues where there is no message in the exception and this simply logsnulland moves ahead.This needs to be changed and we should log the full exception
einstead of just the message.Source connector version
NA
Connector configuration
NA
YugabyteDB version
NA
Warning: Please confirm that this issue does not contain any sensitive information
The text was updated successfully, but these errors were encountered: