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

DBZ-2418 More meaningful error message in case of incorrect credentials #1748

Merged
merged 2 commits into from Aug 12, 2020

Conversation

gunnarmorling
Copy link
Member

This is called only once anyways, so there's no need for storing the info
in a field in PostgresConnection. This allows PostgresConnector#validate()
bring up a more meaningful error message in case of incorrect credentials
and other incorrect connection configuration.
Copy link
Contributor

@jpechane jpechane left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gunnarmorling LGTM, you can merge it. I just recommend a last check and that's priming of TypeRegistry. It can genereate SQL error too but from my reading of the code the connection is validated before a connection that requires type registry is created. But better to doublecheck.

@gunnarmorling
Copy link
Member Author

Yes, right. The type registry will only be required when getting a connection from with the task class. Whereas validate() on the connector class is called before that. Not sure about embedded / DBZ Server, though.

@gunnarmorling gunnarmorling merged commit 26b51e0 into debezium:master Aug 12, 2020
@gunnarmorling gunnarmorling deleted the DBZ-2418 branch August 12, 2020 07:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants