Skip to content

Commit 3e8252b

Browse files
RayOffiahRayOffiah
committed
[DOC-12496]: Create release note for Couchbase Server 7.6.3
1 parent beb3dc5 commit 3e8252b

File tree

3 files changed

+117
-2
lines changed

3 files changed

+117
-2
lines changed

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,10 @@
11
= Release Notes for Couchbase Server 7.6
22
:page-aliases: analytics:releasenote
3-
:description: Couchbase Server 7.6.0 introduces multiple new features and fixes, as well as some deprecations and removals.
3+
:description: Couchbase Server 7.6.x introduces multiple new features and fixes, as well as some deprecations and removals.
44
:page-toclevels: 2
55

6+
include::partial$docs-server-7.6.3-release-note.adoc[]
7+
68
include::partial$docs-server-7.6.2-release-note.adoc[]
79

810
include::partial$docs-server-7.6.1-release-note.adoc[]

‎modules/release-notes/partials/docs-server-7.6.2-release-note.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ The upgrade corrupted existing indexes requiring you to drop and rebuild them.
6161

6262
|===
6363

64-
[#query_services_762]
64+
6565
==== Query Service
6666
[#table-fixed-issues-762-query-service,cols="10,40,40"]
6767
|===
@@ -200,8 +200,10 @@ This release contains the following known issues:
200200
|===
201201
|Issue | Description | Workaround
202202

203+
// tag::MB-62220[]
203204
| https://issues.couchbase.com/browse/MB-62220[MB-62220]
204205
| Dropped replicas are not rebuilt during swap rebalance
205206
| Drop and then recreate the indexes.
207+
// end::MB-62220[]
206208

207209
|===

‎modules/release-notes/partials/docs-server-7.6.3-release-note.adoc

Lines changed: 111 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,111 @@
1+
== Release 7.6.3 (September 2024)
2+
3+
Couchbase Server 7.6.3 was released in September 2024. This maintenance release contains new features and fixes several known issues.
4+
5+
For detailed information on new features and enhancements, please see xref:introduction:whats-new.adoc[].
6+
7+
[#fixed-issues-763]
8+
=== Fixed Issues
9+
10+
This release contains the following fixes:
11+
12+
==== Cluster Manager
13+
14+
[#table-fixed-issues-763-cluster-manager,cols="10,40,40"]
15+
|===
16+
|Issue | Description | Resolution
17+
18+
| https://jira.issues.couchbase.com/browse/MB-63070[MB-63070]
19+
| An issue occurred where `cbcollect_info` did not process some `<ud>…</ud>` tags, especially when they were present at the end of the file or inside binary data. As a result, some logs that should have been redacted were not redacted.
20+
| Issue resolved.
21+
22+
|===
23+
24+
==== Storage Engine
25+
[#table-fixed-issues-763-storage-engine,cols="10,40,40"]
26+
|===
27+
|Issue | Description | Resolution
28+
29+
| https://jira.issues.couchbase.com/browse/MB-62984[MB-62984]
30+
| When a Couchbase Data Service experiences a hard failover or crashes with data loss, DCP clients (like those used with Elasticsearch and Kafka) might receive incomplete or partial snapshots of the data. This incomplete data can lead to rare situations (edge cases) where the Data Service ends up crashing repeatedly.
31+
| Issue resolved.
32+
33+
| https://jira.issues.couchbase.com/browse/MB-63261[MB-63261]
34+
| An issue occurred caused by a race condition in the index recovery code path, which may result in item count mismatch and wrong query results. Prior to Release 7.6.0, this issue may occur during an Indexer restart. However, as part of the file-based rebalance process introduced in 7.6.0, a recovery of the index is performed after the index is moved, which increases the likelihood that this race condition might be reached.
35+
| Issue resolved.
36+
37+
|===
38+
39+
40+
==== Query Service
41+
[#table-fixed-issues-763-query-service,cols="10,40,40"]
42+
|===
43+
|Issue | Description | Resolution
44+
45+
| https://jira.issues.couchbase.com/browse/MB-63024[MB-63024]
46+
a| A query may return the error `Nested aggregates not allowed` under the following conditions:
47+
48+
* query contains in its FROM clause a subquery used as the inner of a join
49+
* the subquery is used as an inner of a nested-loop join in query plan
50+
* the subquery only accesses a single keyspace (i.e., no joins/nests/unnests)
51+
* the subquery contains one or more aggregates (e.g., COUNT) in its projection
52+
* the subquery contains a `GROUP BY` clause, and the `GROUP BY` list does not match index key order of any secondary indexes defined
53+
* a secondary index exists that allows index group/aggregate pushdown for the subquery
54+
* the cost-based optimizer is `ON` (which is the default), and a previous `UPDATE STATISTICS/ANALYZE` command has been run on the keyspace referenced in the subquery.
55+
| Issue resolved.
56+
57+
| https://jira.issues.couchbase.com/browse/MB-63060[MB-63060]
58+
| An issue occurred when migrating nested UDFs to any 7.6.x release from a previous version. In cases when an inline UDF called another UDF, query nodes became unresponsive.
59+
| Issue resolved.
60+
61+
| https://jira.issues.couchbase.com/browse/MB-63078[MB-63078]
62+
a| When upgrading to a 7.6.x release, if buckets were loaded by Query nodes before they were fully migrated to 7.6.x format, Query continually reloaded the bucket on access, leading to degraded performance. This issue has been resolved in 7.6.3.
63+
| Issue resolved.
64+
65+
| https://jira.issues.couchbase.com/browse/MB-63147[MB-63147]
66+
| An issue occurred with user-defined functions (UDFs) that contained queries defined with a common-table expression (CTE). If the CTE contained references to the UDF arguments, the execution of the UDF returned an error indicating “correlation reference `<with_alias>` is not allowed.”
67+
| Issue resolved.
68+
69+
|===
70+
71+
==== Index Service
72+
[#table-fixed-issues-763-index-service,cols="10,40,40"]
73+
|===
74+
|Issue | Description | Resolution
75+
76+
| https://jira.issues.couchbase.com/browse/MB-63193[MB-63193]
77+
| An issue in the rebalancer code caused several partitions to miss streaming mutations when partitioned indexes were moved during file-based rebalance. This issue resulted in corrupt indexes, as not all data will be processed. The issue occurred only with partitioned indexes when file-based rebalance was enabled.
78+
| Issue resolved.
79+
80+
|===
81+
82+
83+
==== Analytics Service
84+
[#table-fixed-issues-763-anaytics-service,cols="10,40,40"]
85+
|===
86+
|Issue | Description | Resolution
87+
88+
| https://jira.issues.couchbase.com/browse/MB-62923[MB-62923]
89+
| TBD.
90+
| Issue resolved.
91+
92+
| https://jira.issues.couchbase.com/browse/MB-62949[MB-62949]|
93+
When a query encounters a failure, the details of the exception can get masked by subsequent exceptions, leading to the loss of the root cause of the query failure.
94+
| Issue resolved.
95+
|===
96+
97+
98+
[#known-issues-763]
99+
=== Known Issues
100+
101+
This release contains the following known issues:
102+
103+
104+
==== Index Service
105+
[#table-known-issues-763-index-service, cols="10,40,40"]
106+
|===
107+
|Issue | Description | Workaround
108+
109+
include::partial$docs-server-7.6.2-release-note.adoc[tag="MB-62220"]
110+
111+
|===

0 commit comments

Comments
 (0)