Bump com.clickhouse:clickhouse-jdbc from 0.9.8 to 0.10.0

[dependabot]

Bumps com.clickhouse:clickhouse-jdbc from 0.9.8 to 0.10.0.

Release notes

Sourced from com.clickhouse:clickhouse-jdbc's releases.

Release v0.10.0

Release Migration Guide

Breaking Changes

• [jdbc-v2] The driver no longer hardcodes the server settings async_insert=0 and wait_end_of_query=0 on every JDBC connection. This unblocks two scenarios that previously did not work: overriding these settings per connection or per statement, and using the driver against read-only profiles that disallow SETTINGS overrides. There are two consequences:

  • The driver now follows the server-side defaults for these settings (note: starting with ClickHouse 26.3, async_insert defaults to 1). Removing the explicit wait_end_of_query=0 is a no-op against server defaults but lets users opt in to wait_end_of_query=1.
  • The row count returned by java.sql.Statement.executeUpdate(java.lang.String) (and the matching PreparedStatement method) is no longer guaranteed to be accurate for INSERT statements when the server runs them asynchronously, and parsing/data errors in the INSERT body may not surface synchronously as a SQLException. Previously these were accurate because inserts were forced to be synchronous (see also ClickHouse/ClickHouse#57768). To restore the previous behavior, set async_insert=0 (or wait_for_async_insert=1) per connection as server setting. Read more about asynchronous insert: https://clickhouse.com/docs/optimize/asynchronous-inserts.

  (ClickHouse/clickhouse-java#2652, ClickHouse/clickhouse-java#2825)

• [client-v2] Client.Builder#build() now throws ClientMisconfigurationException instead of IllegalArgumentException for authentication and SSL misconfiguration (missing credentials, conflicting authentication methods, missing client certificate when SSL authentication is enabled, and trust store used together with a client certificate). Callers that relied on catching IllegalArgumentException from build() for these cases must catch ClientMisconfigurationException (which extends RuntimeException via ClientException). (ClickHouse/clickhouse-java#2812)

• [client-v2] Combining setUsername(...) + setPassword(...) with a custom Authorization HTTP header ( httpHeader(HttpHeaders.AUTHORIZATION, ...)) now fails at Client.Builder#build() with ClientMisconfigurationException unless HTTP Basic authentication is explicitly disabled via useHTTPBasicAuth(false). Previously this combination was accepted and the custom Authorization header overrode the user/password at request time. (ClickHouse/clickhouse-java#2812)

• [client-v2] The access_token configuration property (set via Client.Builder#setAccessToken(String) or directly through setOption) is now actually applied to outgoing requests as the Authorization HTTP header value verbatim. Previously the value was stored under access_token but never sent on the wire, so providing it alone had no effect on authentication. Callers must include the scheme prefix themselves (e.g. setAccessToken("Bearer <token>")), or use useBearerTokenAuth(String) which prepends Bearer automatically. (ClickHouse/clickhouse-java#2812)

• [client-v2] Client.Builder#useBearerTokenAuth(String) now stores the bearer token under the access_token configuration key (with the Bearer prefix) instead of writing it directly into http_header_authorization. The HTTP wire format is unchanged, but the token is no longer observable through Client#getReadOnlyConfig() under the http_header_authorization key. (ClickHouse/clickhouse-java#2812)

• [client-v2] Fixed inconsistent use of executionTimeout parameter in Client component. The timeout was previously set in milliseconds but mistakenly retrieved and used in seconds in some places. Now it correctly uses milliseconds consistently. (ClickHouse/clickhouse-java#2358)

• [client-v2] The public ClickHouseBinaryFormatWriter interface gained two methods, setString(String, byte[]) and setString(int, byte[]), for writing raw String/FixedString bytes. Code that only uses the interface is unaffected, but any third party that implements ClickHouseBinaryFormatWriter directly is source- and binary-incompatible until it adds these methods (recompiling against the new version is required; otherwise an AbstractMethodError can occur at runtime).

• [client-v2] HTTP 503 Service Unavailable responses are now surfaced as a connection-style failure (

... (truncated)

Changelog

Sourced from com.clickhouse:clickhouse-jdbc's changelog.

0.10.0,

Release Migration Guide

Breaking Changes

• [jdbc-v2] The driver no longer hardcodes the server settings async_insert=0 and wait_end_of_query=0 on every JDBC connection. This unblocks two scenarios that previously did not work: overriding these settings per connection or per statement, and using the driver against read-only profiles that disallow SETTINGS overrides. There are two consequences:

  • The driver now follows the server-side defaults for these settings (note: starting with ClickHouse 26.3, async_insert defaults to 1). Removing the explicit wait_end_of_query=0 is a no-op against server defaults but lets users opt in to wait_end_of_query=1.
  • The row count returned by java.sql.Statement.executeUpdate(java.lang.String) (and the matching PreparedStatement method) is no longer guaranteed to be accurate for INSERT statements when the server runs them asynchronously, and parsing/data errors in the INSERT body may not surface synchronously as a SQLException. Previously these were accurate because inserts were forced to be synchronous (see also ClickHouse/ClickHouse#57768). To restore the previous behavior, set async_insert=0 (or wait_for_async_insert=1) per connection as server setting. Read more about asynchronous insert: https://clickhouse.com/docs/optimize/asynchronous-inserts.

  (ClickHouse/clickhouse-java#2652, ClickHouse/clickhouse-java#2825)

• [client-v2] Client.Builder#build() now throws ClientMisconfigurationException instead of IllegalArgumentException for authentication and SSL misconfiguration (missing credentials, conflicting authentication methods, missing client certificate when SSL authentication is enabled, and trust store used together with a client certificate). Callers that relied on catching IllegalArgumentException from build() for these cases must catch ClientMisconfigurationException (which extends RuntimeException via ClientException). (ClickHouse/clickhouse-java#2812)

• [client-v2] Combining setUsername(...) + setPassword(...) with a custom Authorization HTTP header ( httpHeader(HttpHeaders.AUTHORIZATION, ...)) now fails at Client.Builder#build() with ClientMisconfigurationException unless HTTP Basic authentication is explicitly disabled via useHTTPBasicAuth(false). Previously this combination was accepted and the custom Authorization header overrode the user/password at request time. (ClickHouse/clickhouse-java#2812)

• [client-v2] The access_token configuration property (set via Client.Builder#setAccessToken(String) or directly through setOption) is now actually applied to outgoing requests as the Authorization HTTP header value verbatim. Previously the value was stored under access_token but never sent on the wire, so providing it alone had no effect on authentication. Callers must include the scheme prefix themselves (e.g. setAccessToken("Bearer <token>")), or use useBearerTokenAuth(String) which prepends Bearer automatically. (ClickHouse/clickhouse-java#2812)

• [client-v2] Client.Builder#useBearerTokenAuth(String) now stores the bearer token under the access_token configuration key (with the Bearer prefix) instead of writing it directly into http_header_authorization. The HTTP wire format is unchanged, but the token is no longer observable through Client#getReadOnlyConfig() under the http_header_authorization key. (ClickHouse/clickhouse-java#2812)

• [client-v2] Fixed inconsistent use of executionTimeout parameter in Client component. The timeout was previously set in milliseconds but mistakenly retrieved and used in seconds in some places. Now it correctly uses milliseconds consistently. (ClickHouse/clickhouse-java#2358)

• [client-v2] The public ClickHouseBinaryFormatWriter interface gained two methods, setString(String, byte[]) and setString(int, byte[]), for writing raw String/FixedString bytes. Code that only uses the interface is

... (truncated)

Commits

• 57aacb1 Merge pull request #3044 from ClickHouse/pre_0.10.0
• abcabfb pre_0.10.0
• c811085 Merge pull request #2951 from ClickHouse/pre_0.10.0-rc2
• 412b1ac pick: added new engines
• 0e38b94 pick: added missing SQL keywords
• 4ef6989 Updated version to 0.10.0-rc
• 62feee4 Update VERSION
• 9dd3229 Merge pull request #2911 from ClickHouse/07/06/26/binary_string_support
• 69cc780 Merge branch 'v0.10.0' into 07/06/26/binary_string_support
• 035d69d Merge pull request #2912 from ClickHouse/07/06/26/cance_http_request
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}