You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Notes:
In previous versions, the Geometry type was aliased to String, but now it is a full-featured type. #83344
Introduce Geometry type. Support reading WKB and WKT formats for it. In previous versions, the Geometry type was aliased to String, but now it is a full-featured type. #83344
[ERROR] 2025-12-17 15:03:47.935 [main] c.c.j.metadata.DatabaseMetaDataImpl - Failed to convert column data type to SQL type: {}
java.lang.IllegalArgumentException: No enum constant com.clickhouse.data.ClickHouseDataType.Geometry
at java.base/java.lang.Enum.valueOf(Enum.java:293)
at com.clickhouse.data.ClickHouseDataType.valueOf(ClickHouseDataType.java:52)
at com.clickhouse.jdbc.metadata.DatabaseMetaDataImpl.lambda$static$2(DatabaseMetaDataImpl.java:1102)
at com.clickhouse.jdbc.internal.DetachedResultSet.createFromResultSet(DetachedResultSet.java:93)
at com.clickhouse.jdbc.metadata.DatabaseMetaDataImpl.getTypeInfo(DatabaseMetaDataImpl.java:1082)
at io.github.linghengqian.SimpleTest.simpleTest(SimpleTest.java:14)
@linghengqian
I've looked into your case - this message is reported because client may not know type and requires upgrade.
In this case JDBC Driver and Client will continue to work except moments when using unknown type. So this exception is not a bug but warning that client found an unknown type.
@linghengqian
I've looked into your case - this message is reported because client may not know type and requires upgrade.
In this case JDBC Driver and Client will continue to work except moments when using unknown type. So this exception is not a bug but warning that client found an unknown type.
Yes, this error log won't prevent the unit tests from running; it only prints out the log under a specific logback configuration. That's why I'm asking if we need to open a new issue for this.
But this logback configuration is really quite common.😂
@linghengqian
we have another test to detect new types on HEAD and latest version of ClickHouse (just in case we missed it).
I will fix the message to be more informative.
Activity
linghengqian commentedon Dec 17, 2025
chernser commentedon Dec 17, 2025
Good dau, @linghengqian !
Caused by this issue. But for the problem that old client may not work with the new CH there is another #2394
Thank you for bringing this - I will update #2394 with your scenario.
chernser commentedon Dec 18, 2025
@linghengqian
I've looked into your case - this message is reported because client may not know type and requires upgrade.
In this case JDBC Driver and Client will continue to work except moments when using unknown type. So this exception is not a bug but warning that client found an unknown type.
linghengqian commentedon Dec 18, 2025
Yes, this error log won't prevent the unit tests from running; it only prints out the log under a specific logback configuration. That's why I'm asking if we need to open a new issue for this.
But this logback configuration is really quite common.😂
chernser commentedon Dec 18, 2025
@linghengqian
we have another test to detect new types on HEAD and latest version of ClickHouse (just in case we missed it).
I will fix the message to be more informative.