|
7 | 7 |
|
8 | 8 | #### Breaking Changes
|
9 | 9 |
|
10 |
| -* Gone exceptions that are not idempotent should not be retried because it is not known if they succeeded for sure. The handling of the exception in this case is left to the user. Fixed retrying write operations when a gone exception occurs in bulk mode. - See [PR 35838](https://github.com/Azure/azure-sdk-for-java/pull/35838) |
11 | 10 | #### Bugs Fixed
|
12 |
| -* Fixed retrying write operations when a gone exception occurs in bulk mode. - See [PR 35838](https://github.com/Azure/azure-sdk-for-java/pull/35838) |
13 |
| -* Fixed request start time in the `CosmosDiagnostics` for individual request responses - See [PR 35705](https://github.com/Azure/azure-sdk-for-java/pull/35705) |
14 |
| -* Fixed an issue where `ConnectionStateListener` tracked staled `Uris` which fails to mark the current `Uris` unhealthy properly - See [PR 36067](https://github.com/Azure/azure-sdk-for-java/pull/36067) |
15 |
| -* Gone exceptions that are not idempotent should not be retried because it is not known if they succeeded for sure. The handling of the exception in this case is left to the user. Fixed retrying write operations when a gone exception occurs in bulk mode. - See [PR 35838](https://github.com/Azure/azure-sdk-for-java/pull/35838) |
16 |
| -* Fixed an issue to update the last unhealthy timestamp for an `Uri` instance only when transitioning to `Unhealthy` from a different health status - See [PR 36083](https://github.com/Azure/azure-sdk-for-java/pull/36083) |
17 | 11 | * Wired `proactiveInit` into the diagnostics to track warmed up containers, proactive connection regions and aggressive warm up duration - See [PR 36111](https://github.com/Azure/azure-sdk-for-java/pull/36111)
|
18 | 12 |
|
19 | 13 | #### Other Changes
|
20 | 14 |
|
| 15 | +### 4.48.1 (2023-08-09) |
| 16 | +> [!IMPORTANT] |
| 17 | +> We strongly recommend our customers to use version 4.48.1 and above. |
| 18 | +#### Bugs Fixed |
| 19 | +* Fixed request start time in the `CosmosDiagnostics` for individual request responses - See [PR 35705](https://github.com/Azure/azure-sdk-for-java/pull/35705) |
| 20 | +* Fixed an issue where `ConnectionStateListener` tracked staled `Uris` which fails to mark the current `Uris` unhealthy properly - See [PR 36067](https://github.com/Azure/azure-sdk-for-java/pull/36067) |
| 21 | +* Gone exceptions that are not idempotent should not be retried because it is not known if they succeeded for sure. The handling of the exception in this case is left to the user. Fixed retrying write operations when a gone exception occurs in bulk mode. - See [PR 35838](https://github.com/Azure/azure-sdk-for-java/pull/35838) |
| 22 | +* Fixed an issue to update the last unhealthy timestamp for an `Uri` instance only when transitioning to `Unhealthy` from a different health status - See [36083](https://github.com/Azure/azure-sdk-for-java/pull/36083) |
| 23 | +* Improved the channel health check flow to deem a channel unhealthy when it sees consecutive cancellations. - See [PR 36225](https://github.com/Azure/azure-sdk-for-java/pull/36225) |
| 24 | +* Optimized the replica validation flow to validate replica health with `Unknown` health status only when the replica is |
| 25 | +used by a container which is also part of the connection warm-up flow. - See [PR 36225](https://github.com/Azure/azure-sdk-for-java/pull/36225) |
| 26 | + |
21 | 27 | ### 4.48.0 (2023-07-18)
|
22 | 28 |
|
23 | 29 | #### Bugs Fixed
|
@@ -181,8 +187,6 @@ there are non-existent document IDs also passed through the API - See [PR 35513]
|
181 | 187 | * Added option to set throughput control group name on per-request level for batch and bulk operations. - See [PR 31362](https://github.com/Azure/azure-sdk-for-java/pull/31362)
|
182 | 188 |
|
183 | 189 | ### 4.37.1 (2022-10-07)
|
184 |
| -> [!IMPORTANT] |
185 |
| -> We strongly recommend our customers to use version 4.37.1 and above. |
186 | 190 | #### Bugs Fixed
|
187 | 191 | * Fixed incorrect RU metric reporting in micrometer metrics. - See [PR 31307](https://github.com/Azure/azure-sdk-for-java/pull/31307)
|
188 | 192 | * Enabled failover to preferred locations in the case of single-write/multi-read region enabled account for read in Gateway mode and for metadata requests in Direct mode. - More details about the [Bug: Cosmos DB Client gets stuck in timeout retry loop](https://github.com/Azure/azure-sdk-for-java/issues/31260#issue-1396454421). - See [PR 31314](https://github.com/Azure/azure-sdk-for-java/pull/31314)
|
|
0 commit comments