Skip to content

Commit 21c372d

Browse files
Gardening
1 parent c8a6f0e commit 21c372d

1 file changed

Lines changed: 25 additions & 8 deletions

File tree

modules/project-docs/pages/sdk-release-notes.adoc

Lines changed: 25 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,10 @@ We always recommend using the latest version of the SDK -- it contains all of th
2727
All patch releases for each dot minor release should be API compatible, and safe to upgrade;
2828
any changes to expected behavior are noted in the release notes that follow.
2929

30+
Version 3.8 of the Java SDK implements the 3.7 xref:compatibility.adoc#api-version[SDK API].
31+
See the xref:compatibility.adoc#couchbase-feature-availability-matrix[compatibility pages] for more information on feature compatibility with different versions of Couchbase Server.
32+
33+
3034
////
3135
# get version numbers like this
3236
src=../couchbase-jvm-clients
@@ -64,24 +68,35 @@ Optional artifacts on top of this SDK version are tested for the following compa
6468
|=======================
6569

6670

67-
### Bug
71+
==== Bugfixes
6872

69-
[JVMCBC-1628](https://couchbasecloud.atlassian.net/browse/JVMCBC-1628) Specifying DISABLE\_READ\_SKEW\_DETECTION causes transactional getMulti to fail
73+
* https://couchbasecloud.atlassian.net/browse/JVMCBC-1628[JVMCBC-1628]:
74+
Specifying `DISABLE_READ_SKEW_DETECTION` was causing transactional `getMulti` to fail.
75+
This has now been fixed.
7076

71-
### New Feature
77+
==== New Features
7278

73-
[JVMCBC-1602](https://couchbasecloud.atlassian.net/browse/JVMCBC-1602) Application Telemetry \(Phase 2\)
79+
* https://couchbasecloud.atlassian.net/browse/JVMCBC-1602:[JVMCBC-1602]:
80+
Application Telemetry improvements.
7481

75-
### Improvement
82+
==== Improvements
7683

77-
[JCBC-2183](https://couchbasecloud.atlassian.net/browse/JCBC-2183) Implement ExtGetMulti (aka Enhanced Read Committed Isolation)
84+
https://couchbasecloud.atlassian.net/browse/JCBC-2183[JCBC-2183]:
85+
Implemented `ExtGetMulti` (aka Enhanced Read Committed Isolation).
86+
87+
https://couchbasecloud.atlassian.net/browse/JCBC-2186[JCBC-2186]:
88+
Updated Bucket & Storage Support in SDKs.
89+
90+
https://couchbasecloud.atlassian.net/browse/JCBC-2186[JCBC-2147]:
91+
Added `PREFERRED_SERVER_GROUP_OR_ALL_AVAILABLE` support.
7892

79-
[JCBC-2186](https://couchbasecloud.atlassian.net/browse/JCBC-2186) Update Bucket & Storage Support in SDKs
8093

81-
[JCBC-2147](https://couchbasecloud.atlassian.net/browse/JCBC-2186) Add PREFERRED_SERVER_GROUP_OR_ALL_AVAILABLE support
8294

8395
== Java SDK 3.7 Releases
8496

97+
Version 3.7 of the Java SDK implements the 3.6 xref:compatibility.adoc#api-version[SDK API].
98+
See the xref:compatibility.adoc#couchbase-feature-availability-matrix[compatibility pages] for more information on feature compatibility with different versions of Couchbase Server.
99+
85100

86101
=== Version 3.7.9 (11 March 2025)
87102

@@ -186,12 +201,14 @@ Optional artifacts on top of this SDK version are tested for the following compa
186201
|=======================
187202

188203
==== Bug Fixes
204+
189205
* https://jira.issues.couchbase.com/browse/JVMCBC-1592[JVMCBC-1592]:
190206
When fetching fresh cluster topology information for a bucket, the SDK now dispatches the request to a random eligible node instead of using a round-robin algorithm. Randomizing the node selection avoids a pathological condition where if the number of open buckets is equal to the number of nodes, and one of the nodes is degraded, the config refresh attempt for a particular bucket would fail repeatedly because it was always sent to the degraded node.
191207
* https://jira.issues.couchbase.com/browse/JCBC-2152[JCBC-2152]:
192208
Return the inserted document in the form of a TransactionGetResult instead of the old content from the Get operation.
193209

194210
==== Improvements
211+
195212
* https://jira.issues.couchbase.com/browse/JVMCBC-1585[JVMCBC-1585]:
196213
When a thread executing clusterOrScope.queryStreaming() is interrupted, the thrown CancellationException now has the original InterruptedException as its cause.
197214
* https://jira.issues.couchbase.com/browse/JCBC-2174[JCBC-2174]:

0 commit comments

Comments
 (0)