Skip to content

Commit c74bd36

Browse files
committed
Formated changelog. Updated release number
1 parent 4b06e2b commit c74bd36

1 file changed

Lines changed: 10 additions & 3 deletions

File tree

CHANGELOG.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@
6767
The Gradle wrapper and build scripts were removed and each project now has a standalone `pom.xml`.
6868
(https://github.com/ClickHouse/clickhouse-java/issues/2915)
6969

70-
## 0.10.0-rc1,
70+
## 0.10.0,
7171

7272
[Release Migration Guide](docs/releases/0_10_0.md)
7373

@@ -115,7 +115,11 @@
115115
previously set in milliseconds but mistakenly retrieved and used in seconds in some places. Now it correctly uses
116116
milliseconds consistently. (https://github.com/ClickHouse/clickhouse-java/issues/2358)
117117

118-
- **[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).
118+
- **[client-v2]** The public `ClickHouseBinaryFormatWriter` interface gained two methods, `setString(String, byte[])`
119+
and `setString(int, byte[])`, for writing raw `String`/`FixedString` bytes. Code that only *uses* the interface is
120+
unaffected, but any third party that *implements* `ClickHouseBinaryFormatWriter` directly is source- and
121+
binary-incompatible until it adds these methods (recompiling against the new version is required; otherwise an
122+
`AbstractMethodError` can occur at runtime).
119123

120124
- **[client-v2]** HTTP `503 Service Unavailable` responses are now surfaced as a connection-style failure (
121125
`java.net.ConnectException`) and are retried by default. Previously a `503` was treated as a server error (
@@ -229,7 +233,10 @@ like `ch_db_01`. This is mostly used in k8s environment. (https://github.com/Cli
229233

230234
- **[repo]** Added a contribution guide. Please review and send us your feedback. (https://github.com/ClickHouse/clickhouse-java/pull/2859)
231235

232-
- **[client-v2]** Added endpoint failover support: when multiple endpoints are configured and a request fails with a retryable error (connect timeout, connection refused, HTTP 503, etc.), the client now automatically retries against the next available endpoint instead of always targeting the first one. Failed endpoints are quarantined for 30 seconds before being retried. (https://github.com/ClickHouse/clickhouse-java/issues/2855)
236+
- **[client-v2]** Added endpoint failover support: when multiple endpoints are configured and a request fails with a
237+
retryable error (connect timeout, connection refused, HTTP 503, etc.), the client now automatically retries against
238+
the next available endpoint instead of always targeting the first one. Failed endpoints are quarantined for 30 seconds
239+
before being retried. (https://github.com/ClickHouse/clickhouse-java/issues/2855)
233240

234241
### Bug Fixes
235242

0 commit comments

Comments
 (0)