dependabot[bot] opened a new pull request, #25676: URL: https://github.com/apache/camel/pull/25676
Bumps [com.clickhouse:client-v2](https://github.com/ClickHouse/clickhouse-java) from 0.9.8 to 0.10.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/ClickHouse/clickhouse-java/releases";>com.clickhouse:client-v2's releases</a>.</em></p> <blockquote> <h2>Release v0.10.0</h2> <p><a href="https://github.com/ClickHouse/clickhouse-java/blob/HEAD/docs/releases/0_10_0.md";>Release Migration Guide</a></p> <h2>Breaking Changes</h2> <ul> <li> <p><strong>[jdbc-v2]</strong> The driver no longer hardcodes the server settings <code>async_insert=0</code> and <code>wait_end_of_query=0</code> 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 <code>SETTINGS</code> overrides. There are two consequences:</p> <ul> <li>The driver now follows the server-side defaults for these settings (note: starting with ClickHouse 26.3, <code>async_insert</code> defaults to <code>1</code>). Removing the explicit <code>wait_end_of_query=0</code> is a no-op against server defaults but lets users opt in to <code>wait_end_of_query=1</code>.</li> <li>The row count returned by <code>java.sql.Statement.executeUpdate(java.lang.String)</code> (and the matching <code>PreparedStatement</code> 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 <code>SQLException</code>. Previously these were accurate because inserts were forced to be synchronous (see also <a href="https://redirect.github.com/ClickHouse/ClickHouse/issues/57768";>ClickHouse/ClickHouse#57768</a>). To restore the previous behavior, set <code>async_insert=0</code> (or <code>wait_for_async_insert=1</code>) per connection as server setting. Read more about asynchronous insert: <a href="https://clickhouse.com/docs/optimize/asynchronous-inserts";>https://clickhouse.com/docs/optimize/asynchronous-inserts</a>.</li> </ul> <p>(<a href="https://redirect.github.com/ClickHouse/clickhouse-java/issues/2652";>ClickHouse/clickhouse-java#2652</a>, <a href="https://redirect.github.com/ClickHouse/clickhouse-java/issues/2825";>ClickHouse/clickhouse-java#2825</a>)</p> </li> <li> <p><strong>[client-v2]</strong> <code>Client.Builder#build()</code> now throws <code>ClientMisconfigurationException</code> instead of <code>IllegalArgumentException</code> 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 <code>IllegalArgumentException</code> from <code>build()</code> for these cases must catch <code>ClientMisconfigurationException</code> (which extends <code>RuntimeException</code> via <code>ClientException</code>). (<a href="https://redirect.github.com/ClickHouse/clickhouse-java/pull/2812";>ClickHouse/clickhouse-java#2812</a>)</p> </li> <li> <p><strong>[client-v2]</strong> Combining <code>setUsername(...)</code> + <code>setPassword(...)</code> with a custom <code>Authorization</code> HTTP header ( <code>httpHeader(HttpHeaders.AUTHORIZATION, ...)</code>) now fails at <code>Client.Builder#build()</code> with <code>ClientMisconfigurationException</code> unless HTTP Basic authentication is explicitly disabled via <code>useHTTPBasicAuth(false)</code>. Previously this combination was accepted and the custom <code>Authorization</code> header overrode the user/password at request time. (<a href="https://redirect.github.com/ClickHouse/clickhouse-java/pull/2812";>ClickHouse/clickhouse-java#2812</a>)</p> </li> <li> <p><strong>[client-v2]</strong> The <code>access_token</code> configuration property (set via <code>Client.Builder#setAccessToken(String)</code> or directly through <code>setOption</code>) is now actually applied to outgoing requests as the <code>Authorization</code> HTTP header value verbatim. Previously the value was stored under <code>access_token</code> but never sent on the wire, so providing it alone had no effect on authentication. Callers must include the scheme prefix themselves (e.g. <code>setAccessToken("Bearer <token>")</code>), or use <code>useBearerTokenAuth(String)</code> which prepends <code>Bearer </code> automatically. (<a href="https://redirect.github.com/ClickHouse/clickhouse-java/pull/2812";>ClickHouse/clickhouse-java#2812</a>)</p> </li> <li> <p><strong>[client-v2]</strong> <code>Client.Builder#useBearerTokenAuth(String)</code> now stores the bearer token under the <code>access_token</code> configuration key (with the <code>Bearer </code> prefix) instead of writing it directly into <code>http_header_authorization</code>. The HTTP wire format is unchanged, but the token is no longer observable through <code>Client#getReadOnlyConfig()</code> under the <code>http_header_authorization</code> key. (<a href="https://redirect.github.com/ClickHouse/clickhouse-java/pull/2812";>ClickHouse/clickhouse-java#2812</a>)</p> </li> <li> <p><strong>[client-v2]</strong> Fixed inconsistent use of <code>executionTimeout</code> parameter in <code>Client</code> component. The timeout was previously set in milliseconds but mistakenly retrieved and used in seconds in some places. Now it correctly uses milliseconds consistently. (<a href="https://redirect.github.com/ClickHouse/clickhouse-java/issues/2358";>ClickHouse/clickhouse-java#2358</a>)</p> </li> <li> <p><strong>[client-v2]</strong> The public <code>ClickHouseBinaryFormatWriter</code> interface gained two methods, <code>setString(String, byte[])</code> and <code>setString(int, byte[])</code>, for writing raw <code>String</code>/<code>FixedString</code> bytes. Code that only <em>uses</em> the interface is unaffected, but any third party that <em>implements</em> <code>ClickHouseBinaryFormatWriter</code> directly is source- and binary-incompatible until it adds these methods (recompiling against the new version is required; otherwise an <code>AbstractMethodError</code> can occur at runtime).</p> </li> <li> <p><strong>[client-v2]</strong> HTTP <code>503 Service Unavailable</code> responses are now surfaced as a connection-style failure (</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/ClickHouse/clickhouse-java/blob/main/CHANGELOG.md";>com.clickhouse:client-v2's changelog</a>.</em></p> <blockquote> <h2>0.10.0,</h2> <p><a href="https://github.com/ClickHouse/clickhouse-java/blob/main/docs/releases/0_10_0.md";>Release Migration Guide</a></p> <h3>Breaking Changes</h3> <ul> <li> <p><strong>[jdbc-v2]</strong> The driver no longer hardcodes the server settings <code>async_insert=0</code> and <code>wait_end_of_query=0</code> 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 <code>SETTINGS</code> overrides. There are two consequences:</p> <ul> <li>The driver now follows the server-side defaults for these settings (note: starting with ClickHouse 26.3, <code>async_insert</code> defaults to <code>1</code>). Removing the explicit <code>wait_end_of_query=0</code> is a no-op against server defaults but lets users opt in to <code>wait_end_of_query=1</code>.</li> <li>The row count returned by <code>java.sql.Statement.executeUpdate(java.lang.String)</code> (and the matching <code>PreparedStatement</code> 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 <code>SQLException</code>. Previously these were accurate because inserts were forced to be synchronous (see also <a href="https://redirect.github.com/ClickHouse/ClickHouse/issues/57768";>ClickHouse/ClickHouse#57768</a>). To restore the previous behavior, set <code>async_insert=0</code> (or <code>wait_for_async_insert=1</code>) per connection as server setting. Read more about asynchronous insert: <a href="https://clickhouse.com/docs/optimize/asynchronous-inserts";>https://clickhouse.com/docs/optimize/asynchronous-inserts</a>.</li> </ul> <p>(<a href="https://redirect.github.com/ClickHouse/clickhouse-java/issues/2652";>ClickHouse/clickhouse-java#2652</a>, <a href="https://redirect.github.com/ClickHouse/clickhouse-java/issues/2825";>ClickHouse/clickhouse-java#2825</a>)</p> </li> <li> <p><strong>[client-v2]</strong> <code>Client.Builder#build()</code> now throws <code>ClientMisconfigurationException</code> instead of <code>IllegalArgumentException</code> 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 <code>IllegalArgumentException</code> from <code>build()</code> for these cases must catch <code>ClientMisconfigurationException</code> (which extends <code>RuntimeException</code> via <code>ClientException</code>). (<a href="https://redirect.github.com/ClickHouse/clickhouse-java/pull/2812";>ClickHouse/clickhouse-java#2812</a>)</p> </li> <li> <p><strong>[client-v2]</strong> Combining <code>setUsername(...)</code> + <code>setPassword(...)</code> with a custom <code>Authorization</code> HTTP header ( <code>httpHeader(HttpHeaders.AUTHORIZATION, ...)</code>) now fails at <code>Client.Builder#build()</code> with <code>ClientMisconfigurationException</code> unless HTTP Basic authentication is explicitly disabled via <code>useHTTPBasicAuth(false)</code>. Previously this combination was accepted and the custom <code>Authorization</code> header overrode the user/password at request time. (<a href="https://redirect.github.com/ClickHouse/clickhouse-java/pull/2812";>ClickHouse/clickhouse-java#2812</a>)</p> </li> <li> <p><strong>[client-v2]</strong> The <code>access_token</code> configuration property (set via <code>Client.Builder#setAccessToken(String)</code> or directly through <code>setOption</code>) is now actually applied to outgoing requests as the <code>Authorization</code> HTTP header value verbatim. Previously the value was stored under <code>access_token</code> but never sent on the wire, so providing it alone had no effect on authentication. Callers must include the scheme prefix themselves (e.g. <code>setAccessToken("Bearer <token>")</code>), or use <code>useBearerTokenAuth(String)</code> which prepends <code>Bearer </code> automatically. (<a href="https://redirect.github.com/ClickHouse/clickhouse-java/pull/2812";>ClickHouse/clickhouse-java#2812</a>)</p> </li> <li> <p><strong>[client-v2]</strong> <code>Client.Builder#useBearerTokenAuth(String)</code> now stores the bearer token under the <code>access_token</code> configuration key (with the <code>Bearer </code> prefix) instead of writing it directly into <code>http_header_authorization</code>. The HTTP wire format is unchanged, but the token is no longer observable through <code>Client#getReadOnlyConfig()</code> under the <code>http_header_authorization</code> key. (<a href="https://redirect.github.com/ClickHouse/clickhouse-java/pull/2812";>ClickHouse/clickhouse-java#2812</a>)</p> </li> <li> <p><strong>[client-v2]</strong> Fixed inconsistent use of <code>executionTimeout</code> parameter in <code>Client</code> component. The timeout was previously set in milliseconds but mistakenly retrieved and used in seconds in some places. Now it correctly uses milliseconds consistently. (<a href="https://redirect.github.com/ClickHouse/clickhouse-java/issues/2358";>ClickHouse/clickhouse-java#2358</a>)</p> </li> <li> <p><strong>[client-v2]</strong> The public <code>ClickHouseBinaryFormatWriter</code> interface gained two methods, <code>setString(String, byte[])</code> and <code>setString(int, byte[])</code>, for writing raw <code>String</code>/<code>FixedString</code> bytes. Code that only <em>uses</em> the interface is</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/ClickHouse/clickhouse-java/commit/57aacb1397ec4f90180cb38c82743ae9eaa22290";><code>57aacb1</code></a> Merge pull request <a href="https://redirect.github.com/ClickHouse/clickhouse-java/issues/3044";>#3044</a> from ClickHouse/pre_0.10.0</li> <li><a href="https://github.com/ClickHouse/clickhouse-java/commit/abcabfb63fdf1f4530342a853b92d9e0cc6fada9";><code>abcabfb</code></a> pre_0.10.0</li> <li><a href="https://github.com/ClickHouse/clickhouse-java/commit/c811085502f7408e2b28314d078a2e48eec8878e";><code>c811085</code></a> Merge pull request <a href="https://redirect.github.com/ClickHouse/clickhouse-java/issues/2951";>#2951</a> from ClickHouse/pre_0.10.0-rc2</li> <li><a href="https://github.com/ClickHouse/clickhouse-java/commit/412b1ac23346e882df7363eb5c3812afea2ee56f";><code>412b1ac</code></a> pick: added new engines</li> <li><a href="https://github.com/ClickHouse/clickhouse-java/commit/0e38b94b2b6318b1ae33ca595ca558e2f3717c79";><code>0e38b94</code></a> pick: added missing SQL keywords</li> <li><a href="https://github.com/ClickHouse/clickhouse-java/commit/4ef698970b563e06a99cc95e70cdcbc959147697";><code>4ef6989</code></a> Updated version to 0.10.0-rc</li> <li><a href="https://github.com/ClickHouse/clickhouse-java/commit/62feee4c13084b42e644bf24b75084bf21e7a658";><code>62feee4</code></a> Update VERSION</li> <li><a href="https://github.com/ClickHouse/clickhouse-java/commit/9dd3229c397c79f0d52b61dca55a358b87f5e68b";><code>9dd3229</code></a> Merge pull request <a href="https://redirect.github.com/ClickHouse/clickhouse-java/issues/2911";>#2911</a> from ClickHouse/07/06/26/binary_string_support</li> <li><a href="https://github.com/ClickHouse/clickhouse-java/commit/69cc780472db9ff6ae8728c680de47a0cc0a8c48";><code>69cc780</code></a> Merge branch 'v0.10.0' into 07/06/26/binary_string_support</li> <li><a href="https://github.com/ClickHouse/clickhouse-java/commit/035d69d47a6232ac8990b35bf96ddd7a2c651fce";><code>035d69d</code></a> Merge pull request <a href="https://redirect.github.com/ClickHouse/clickhouse-java/issues/2912";>#2912</a> from ClickHouse/07/06/26/cance_http_request</li> <li>Additional commits viewable in <a href="https://github.com/ClickHouse/clickhouse-java/compare/v0.9.8...v0.10.0";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
