You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/project-docs/pages/sdk-release-notes.adoc
+7-50Lines changed: 7 additions & 50 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
= Release Notes
2
2
:description: Release notes and download archive for the Couchbase .NET Client.
3
-
:page-topic-type: reference
3
+
// :page-topic-type: project doc
4
4
:page-aliases: relnotes-dotnet-sdk
5
5
:page-partial:
6
6
@@ -18,12 +18,6 @@ The full installation instructions that were previously on this page can now be
18
18
19
19
Version 3.4.1 is the second release of the 3.4 series.
20
20
21
-
=== Special Note
22
-
23
-
* During a rebalance upgrade from 6.x (or any earlier version) to 7.x, in mixed mode (where you are communicating with Couchbase Server whilst some but not all nodes are upgraded), there is a known issue where data may be written to the wrong location.
24
-
The solution is to either upgrade to `3.2.9` or greater, or to pause application processing so there are no writes until you have upgraded all nodes.
25
-
If you encounter a similar situation during migration and need help with mitigation, please contact our support team.
* During a rebalance upgrade from 6.x (or any earlier version) to 7.x, in mixed mode (where you are communicating with Couchbase Server whilst some but not all nodes are upgraded), there is a known issue where data may be written to the wrong location.
53
-
The solution is to either upgrade to `3.2.9` or greater, or to pause application processing so there are no writes until you have upgraded all nodes.
54
-
If you encounter a similar situation during migration and need help with mitigation, please contact our support team.
55
-
56
44
=== Fixed Issues
57
45
58
46
* https://issues.couchbase.com/browse/NCBC-3246[NCBC-3246]: EndpointDiagnostics.State always returns "Authenticating" for KV and not implemented per RFC
* During a rebalance upgrade from 6.x (or any earlier version) to 7.x, in mixed mode (where you are communicating with Couchbase Server whilst some but not all nodes are upgraded), there is a known issue where data may be written to the wrong location.
79
-
The solution is to either upgrade to `3.2.9` or greater, or to pause application processing so there are no writes until you have upgraded all nodes.
80
-
If you encounter a similar situation during migration and need help with mitigation, please contact our support team.
* During a rebalance upgrade from 6.x (or any earlier version) to 7.x, in mixed mode (where you are communicating with Couchbase Server whilst some but not all nodes are upgraded), there is a known issue where data may be written to the wrong location.
118
-
The solution is to either upgrade to `3.2.9` or greater, or to pause application processing so there are no writes until you have upgraded all nodes.
119
-
If you encounter a similar situation during migration and need help with mitigation, please contact our support team.
* During a rebalance upgrade from 6.x (or any earlier version) to 7.x, in mixed mode (where you are communicating with Couchbase Server whilst some but not all nodes are upgraded), there is a known issue where data may be written to the wrong location.
140
-
The solution is to either upgrade to `3.2.9` or greater, or to pause application processing so there are no writes until you have upgraded all nodes.
141
-
If you encounter a similar situation during migration and need help with mitigation, please contact our support team.
* During a rebalance upgrade from 6.x (or any earlier version) to 7x, in mixed mode (where you are communicating with Couchbase Server whilst some but not all nodes are upgraded), there is a known issue where data may be written to the wrong location.
170
-
The solution is to either upgrade to 3.2.9 or greater, or to pause application processing so there are no writes until you have upgraded all nodes.
171
-
If you encounter a similar situation during migration and need help with mitigation, please contact our support team.
* During a rebalance upgrade from 6.x (or any earlier version) to 7x, in mixed mode (where you are communicating with Couchbase Server whilst some but not all nodes are upgraded), there is a known issue where data may be written to the wrong location.
213
-
The solution is to either upgrade to 3.2.9 or greater, or to pause application processing so there are no writes until you have upgraded all nodes.
214
-
If you encounter a similar situation during migration and need help with mitigation, please contact our support team.
* During a rebalance upgrade from 6.x (or any earlier version) to 7x, in mixed mode (where you are communicating with Couchbase Server whilst some but not all nodes are upgraded), there is a known issue where data may be written to the wrong location.
303
-
The solution is to either upgrade to 3.2.9 or greater, or to pause application processing so there are no writes until you have upgraded all nodes.
304
-
If you encounter a similar situation during migration and need help with mitigation, please contact our support team.
Numerous _Alpha_ and _Beta_ releases were made in the run-up to the 3.0 release, and although unsupported, the release notes and download links are retained for archive purposes xref:3.0-pre-release-notes.adoc[here].
0 commit comments