ClickHouse syntax error on each query
See original GitHub issueSystem information:
- Operating system (distribution) and version: Windows 7
- DBeaver version: 22.1.0.202206051253
- Additional extensions: None
Connection specification:
- Database name and version: ClickHouse 22.6.1.1985
- Driver name: com.clickhouse.jdbc.ClickHouseDriver
- Do you use tunnels or proxies (SSH, SOCKS, etc)? : No
Describe the problem you’re observing:
Before each user query to clickhouse dbeaver sends an extra one which fails with log message from clickhouse. Seems like no effect to user queries.
Steps to reproduce, if exist:
Perform any query
Include any warning/errors/backtraces from the logs
ClickHouse error:
2022.06.27 00:34:11.822167 [ 52535 ] {be708644-dd61-4f03-a15f-2658ba4b6b6e} <Error> executeQuery: Code: 62. DB::Exception: Syntax error: failed at position 72 ('Client'): Client as DEFAULT_VALUE, Application name as DESCRIPTION union all select CustomHttpHeaders as NAME, toInt32(0) as MAX_LEN, as DEFAULT_VALUE, Custom HTTP heade. Expected one of: token, Comma, FROM, PREWHERE, WHERE, GROUP BY, WITH, HAVING, WINDOW, ORDER BY, LIMIT, OFFSET, SETTINGS, UNION, EXCEPT, INTERSECT, INTO OUTFILE, FORMAT, end of query. (SYNTAX_ERROR) (version 22.6.1.1985 (official build)) (from 10.50.0.10:52522) (in query: select ApplicationName as NAME, toInt32(0) as MAX_LEN, ClickHouse Java Client as DEFAULT_VALUE, Application name as DESCRIPTION union all select CustomHttpHeaders as NAME, toInt32(0) as MAX_LEN, as DEFAULT_VALUE, Custom HTTP headers as DESCRIPTION union all select CustomHttpParameters as NAME, toInt32(0) as MAX_LEN, as DEFAULT_VALUE, Customer HTTP query parameters as DESCRIPTION), Stack trace (when copying this message, always include the lines below):
Issue Analytics
- State:
- Created a year ago
- Comments:9 (4 by maintainers)
Top GitHub Comments
Apparently
ClickHouse Java Client as DEFAULT_VALUE
should be'ClickHouse Java Client' as DEFAULT_VALUE
- same issue exists in latest patch release. I’ll fix it in next release.Update: actually it’s been fixed in ClickHouse/clickhouse-jdbc#930, so upgrading driver to 0.3.2-patch9 or above will work.
fixed in the scope of #17879