Skip to content

Commit ed4e092

Browse files
RayOffiahRayOffiah
authored
Merge pull request #4083
* [DOC-13969]: Create release note for Couchbase Server 7.6.10 * [DOC-13969]: Create release note for Couchbase Server 7.6.10 * [DOC-13969]: Create release note for Couchbase Server 7.6.10 * [DOC-13969]: Create release note for Couchbase Server 7.6.10 * [DOC-13969]: Create release note for Couchbase Server 7.6.10
1 parent 453b0dc commit ed4e092

2 files changed

Lines changed: 241 additions & 0 deletions

File tree

‎modules/release-notes/pages/relnotes.adoc‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@
44
:page-toclevels: 2
55
:stem:
66

7+
include::partial$docs-server-7.6.10-release-notes.adoc[]
8+
79
include::partial$docs-server-7.6.9-release-note.adoc[]
810

911
include::partial$docs-server-7.6.8-release-note.adoc[]

‎modules/release-notes/partials/docs-server-7.6.10-release-notes.adoc‎

Lines changed: 239 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,239 @@
1+
2+
[#release-7610]
3+
== Release 7.6.10 (February 2026)
4+
5+
Couchbase Server 7.6.10 was released in February 2026.
6+
This maintenance release contains fixes to issues.
7+
8+
== Fixed Issues
9+
10+
11+
12+
13+
=== Cluster Manager
14+
[#table-fixed-issues-7610-cluster-manager, cols='10,40,40']
15+
|===
16+
|Issue | Description | Resolution
17+
18+
19+
|https://jira.issues.couchbase.com/browse/MB-69026/[MB-69026]
20+
21+
a|Addressed an issue with stuck rebalance email alerts in Couchbase Server.
22+
23+
This fix resolves problems observed when "Require encryption (TLS)" was configured, causing alert failures.
24+
25+
| Issue resolved
26+
27+
28+
|https://jira.issues.couchbase.com/browse/MB-69650/[MB-69650]
29+
30+
a|A problem was introduced in 7.6.2 where the presence of a Cloud Native Gateway in the cluster would cause issues for services connecting to the cluster manager.
31+
32+
The presence of Cloud Native Gateway no longer causes these issues.
33+
34+
| Issue resolved
35+
36+
37+
|https://jira.issues.couchbase.com/browse/MB-70441/[MB-70441]
38+
39+
a|The upgrade to Erlang version 26 introduced a change in behavior which requires peer certification when TLS is being used for Alert emails.
40+
The peer certification introduced with the changes for this ticket uses the trusted CA certificates provided by the operating system.
41+
42+
| Issue resolved
43+
44+
45+
|===
46+
47+
48+
49+
=== Data Service
50+
[#table-fixed-issues-7610-data-service, cols='10,40,40']
51+
|===
52+
|Issue | Description | Resolution
53+
54+
55+
|https://jira.issues.couchbase.com/browse/MB-54274/[MB-54274]
56+
57+
a|The recent builds of various Couchbase components incorporate a change in the `kv_engine` to modify the handling of temporary items.
58+
These items, whether initially created or deleted,
59+
are no longer removed immediately from the HashTable.
60+
61+
The primary focus is on ensuring better handling and management of temporary items, enhancing system stability and performance.
62+
These updates are part of ongoing improvements committed to optimizing the `kv_engine` and its interactions within the Couchbase ecosystem.
63+
64+
| Issue resolved
65+
66+
67+
|===
68+
69+
70+
71+
72+
73+
=== XDCR
74+
[#table-fixed-issues-7610-xdcr, cols='10,40,40']
75+
|===
76+
|Issue | Description | Resolution
77+
78+
79+
|https://jira.issues.couchbase.com/browse/MB-70294/[MB-70294]
80+
81+
a|Filter Expressions referencing only the document keys are now applicable on deletions and expirations using the new `filterDeletionsWithExpression` and `filterExpirationsWithExpression` replication settings via the REST API.
82+
83+
| Issue resolved
84+
85+
86+
|===
87+
88+
89+
90+
=== Query Service
91+
[#table-fixed-issues-7610-query-service, cols='10,40,40']
92+
|===
93+
|Issue | Description | Resolution
94+
95+
96+
|https://jira.issues.couchbase.com/browse/MB-68969/[MB-68969]
97+
98+
a|* With multi-collection indexes that contained fields with `include in _all` setting enabled - there was a possibility for false positives to show up for field agnostic (composite field) queries.
99+
This has been addressed by denying the sargability for such indexes.
100+
* Addressed an issue where fields not belonging to a particular keyspace were being included in multi-collection indexes.
101+
* Addressed a bug that could influence composite field (`_all`) availability based on the order in which fields were processed.
102+
103+
| Issue resolved
104+
105+
106+
|https://jira.issues.couchbase.com/browse/MB-69081/[MB-69081]
107+
108+
a|To retrieve a document's expiration, the user had to specify the sub-path explicitly, i.e `META().expiration`.
109+
A call to the `META()` function without the sub-path would return the default expiration value 0 always which was incorrect.
110+
111+
112+
Now, when a user’s query invokes META() function without explicitly specifying the sub-path the document's expiration value is returned.
113+
114+
| Issue resolved
115+
116+
117+
|https://jira.issues.couchbase.com/browse/MB-69083/[MB-69083]
118+
119+
a|Problem:
120+
121+
A query may return an incorrect result under the following conditions:
122+
123+
* query contains one or more joins
124+
* one of the joins involves a sub-query (FROM clause subquery)
125+
* the FROM clause sub-query has a GROUP BY and/or aggregates
126+
* the FROM clause sub-query can take advantage of index group/aggregate pushdown
127+
(this requires an appropriate secondary index)
128+
* CBO is ON, and UPDATE STATISTICS has been run on all keyspaces/indexes involved
129+
130+
| Issue resolved
131+
132+
133+
|https://jira.issues.couchbase.com/browse/MB-69387/[MB-69387]
134+
135+
a|The auto-reprepare feature is available in this release.
136+
It is an opt-in feature that automatically re-prepares a prepared statement before execution if any GSI changes (such as indexes being created or dropped) have occurred since the statement's plan was last created.
137+
This allows prepared statements to adopt better suited indexes in their plans.
138+
139+
140+
Enable this feature by setting bit 23 (0x800000 or 8388608) of the n1ql-feat-ctrl Query setting.
141+
Capella users should contact support to opt in.
142+
143+
| Issue resolved
144+
145+
146+
|https://jira.issues.couchbase.com/browse/MB-69955/[MB-69955]
147+
148+
a|`CYCLE` was added as a KEYWORD for RECURSIVE WITH’s CYCLE sub-clause.
149+
150+
This causes a syntax error when a path or sub-path’s case-insensitive identifier is named `cycle` when users upgraded to a version that supported the recursive with feature https://docs.couchbase.com/server/current/n1ql/n1ql-language-reference/with-recursive.html[WITH recursive clause]
151+
152+
This is now handled by allowing `cycle` keyword as a permitted identifier.
153+
154+
| Issue resolved
155+
156+
157+
|https://jira.issues.couchbase.com/browse/MB-70112/[MB-70112]
158+
159+
a|When a prepared request is made with the `auto_execute` request parameter set as `true`, the request would incorrectly error out with error: `Unrecognizable prepared statement - cause: JSON unmarshalling error: auto_execute did not produce a prepared statement`
160+
161+
In this release the server silently ignores the `auto_execute` request parameter when the request is a prepared request.
162+
163+
| Issue resolved
164+
165+
166+
|===
167+
168+
169+
170+
171+
172+
173+
174+
=== Index Service
175+
[#table-fixed-issues-7610-index-service, cols='10,40,40']
176+
|===
177+
|Issue | Description | Resolution
178+
179+
180+
|https://jira.issues.couchbase.com/browse/MB-69934/[MB-69934]
181+
182+
a|Updated chronology for certain storage API calls to avoid rare corner case of shard metadata mismatch.
183+
184+
| Issue resolved
185+
186+
187+
|https://jira.issues.couchbase.com/browse/MB-69952/[MB-69952]
188+
189+
a|Prior to this release, building a new GSI index on a collection could take an extended period of time in certain scenarios.
190+
191+
The indexer builds a new index using a dedicated DCP stream and later merges it into the common DCP stream that processes incremental mutations.
192+
If mutation processing for the new index lagged behind incremental mutation processing, the DCP stream merge could be significantly delayed.
193+
194+
This release introduces a mechanism to detect such imbalances and dynamically adjust the rate of incremental mutation processing to facilitate faster stream merging.
195+
196+
| Issue resolved
197+
198+
199+
|===
200+
201+
202+
203+
=== Search Service
204+
[#table-fixed-issues-7610-search-service, cols='10,40,40']
205+
|===
206+
|Issue | Description | Resolution
207+
208+
209+
|https://jira.issues.couchbase.com/browse/MB-68969/[MB-68969]
210+
211+
a|* With multi-collection indexes that contained fields with `include in _all` setting enabled - there was a possibility for false positives to show up for field agnostic (composite field) queries.
212+
This has been addressed by denying the sargability for such indexes.
213+
* Addressed an issue where fields not belonging to a particular keyspace were being included in multi-collection indexes.
214+
* Addressed a bug that could influence composite field (`_all`) availability based on the order in which fields were processed.
215+
216+
| Issue resolved
217+
218+
219+
|===
220+
221+
222+
223+
=== Tools
224+
[#table-fixed-issues-7610-tools, cols='10,40,40']
225+
|===
226+
|Issue | Description | Resolution
227+
228+
229+
|https://jira.issues.couchbase.com/browse/MB-70255/[MB-70255]
230+
231+
a|Fixes bug where buckets with cross-cluster versioning enabled (link:https://docs.couchbase.com/server/current/learn/clusters-and-availability/xdcr-enable-crossclusterversioning.html[XDCR enable cross cluster versioning] ) would cause a merge to fail
232+
233+
| Issue resolved
234+
235+
236+
|===
237+
238+
239+

0 commit comments

Comments
 (0)