We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
On some exceptions the JDBC driver prints a whole stack trace to stdout here: https://github.com/ClickHouse/clickhouse-java/blob/main/clickhouse-client/src/main/java/com/clickhouse/client/ClickHouseClient.java#L963
This can mess up structured logging output for an application that uses the ClickHouse JDBC driver.
Should use some common logging framework where the application can control logging from libraries. For example: SLF4J or logback.
Or throw an exception and let the application worry about it.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
On some exceptions the JDBC driver prints a whole stack trace to stdout here: https://github.com/ClickHouse/clickhouse-java/blob/main/clickhouse-client/src/main/java/com/clickhouse/client/ClickHouseClient.java#L963
This can mess up structured logging output for an application that uses the ClickHouse JDBC driver.
Steps to reproduce
Expected behaviour
Should use some common logging framework where the application can control logging from libraries. For example: SLF4J or logback.
Or throw an exception and let the application worry about it.
The text was updated successfully, but these errors were encountered: