clickhouse-java
clickhouse-java copied to clipboard
Java client and JDBC driver for ClickHouse
Hi I am trying to use the r2dbc java client to integrate with Spring webflux and send statements to clickhouse as I am evaluating swapping out Druid for Clickhouse. I...
## Description Users are unable to effectively view and query JSON data types from ClickHouse columns using popular SQL clients like DBeaver (even with the latest ClickHouse driver) and, allegedly,...
## Summary This PR add configuration option to create mapping between host/ip and SNI. The last one will be set each time SSL socket is created to connect to it....
## Description The Spark JDBC V2 data source fails to recognize the UInt64 data type from ClickHouse, resulting in a SparkSQLException. This prevents reading tables that contain UInt64 columns. The...
## Description There is an exception ``` [HY000] Failed to read value for column test Unsupported data type with tag 100 ``` This probably relates to the type mapping in...
It looks like parsing of JDBC URL does not support dash (hyphen) in database name. This results in `Code: 81. DB::Exception: Database test does not exist.` when trying to connect...
## Description ### Steps to reproduce 1. Set up a clickhouse container, I'm running `clickhouse/clickhouse-server:25.2-alpine`. There's a database `test_data`, and it has a table `categories`. See bottom section for the...
### Use case https://github.com/ClickHouse/ClickHouse/pull/81217 brings `Time` and `Time64` support into ClickHouse. See the PR for docs and coding/encoding logic. ### Describe the solution you'd like The client and driver support...
`SQL Error [HY000]: Multiple entries with same key: ...` when working on analysis with new drivers.
### Use case When working with tables with lots of columns I tend to select few interesting columns (to easily see them on the left of displayed results on a...
**connecting to ClickHouse using DBeaver, it prompts: 'Code: 115. DB::Exception: (transport error: 404)',**  **using the following driver:**  **the error details show as bellow:**  **but the connection succeeds...