|
| 1 | + |
| 2 | + |
| 3 | + |
| 4 | +[#release-801] |
| 5 | +== Release 8.0.1 (March 2026) |
| 6 | + |
| 7 | +Couchbase Server 8.0.1 was released in March 2026. |
| 8 | +This maintenance release contains fixes to issues. |
| 9 | + |
| 10 | +[#dlist-fixed-issues-801] |
| 11 | +== Fixed Issues |
| 12 | + |
| 13 | + |
| 14 | + |
| 15 | + |
| 16 | +[#dlist-fixed-issues-801-cluster-manager] |
| 17 | +=== Cluster Manager |
| 18 | + |
| 19 | +*https://jira.issues.couchbase.com/browse/MB-69026/[MB-69026]*:: |
| 20 | + |
| 21 | +Addressed an issue with stuck rebalance email alerts in Couchbase Server. |
| 22 | + |
| 23 | ++ |
| 24 | +
|
| 25 | +This fix resolves problems observed when "Require encryption (TLS)" was configured, |
| 26 | +causing alert failures. |
| 27 | + |
| 28 | +*https://jira.issues.couchbase.com/browse/MB-69650/[MB-69650]*:: |
| 29 | + |
| 30 | +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 | +*https://jira.issues.couchbase.com/browse/MB-70441/[MB-70441]*:: |
| 35 | + |
| 36 | +The upgrade to Erlang version 26 introduced a change in behavior which requires peer certification when TLS is being used for Alert emails. |
| 37 | +The peer certification introduced with the changes for this ticket uses the trusted CA certificates provided by the operating system. |
| 38 | + |
| 39 | + |
| 40 | + |
| 41 | + |
| 42 | + |
| 43 | + |
| 44 | + |
| 45 | + |
| 46 | + |
| 47 | +[#dlist-fixed-issues-801-query-service] |
| 48 | +=== Query Service |
| 49 | + |
| 50 | +*https://jira.issues.couchbase.com/browse/MB-68969/[MB-68969]*:: |
| 51 | + |
| 52 | +* 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. |
| 53 | +This has been addressed by denying the sargability for such indexes. |
| 54 | +* Addressed an issue where fields not belonging to a particular keyspace were being included in multi-collection indexes. |
| 55 | +* Addressed a bug that could influence composite field (`_all`) availability based on the order in which fields were processed. |
| 56 | +
|
| 57 | +*https://jira.issues.couchbase.com/browse/MB-69081/[MB-69081]*:: |
| 58 | + |
| 59 | +To retrieve a document's expiration, |
| 60 | +the user had to specify the sub-path explicitly, |
| 61 | +i.e `META().expiration`. |
| 62 | +A call to the `META()` function without the sub-path would return the default expiration value 0 always which was incorrect. |
| 63 | + |
| 64 | + |
| 65 | ++ |
| 66 | +
|
| 67 | +Now, |
| 68 | +when a user’s query invokes META() function without explicitly specifying the sub-path the document's expiration value is returned. |
| 69 | + |
| 70 | +*https://jira.issues.couchbase.com/browse/MB-69083/[MB-69083]*:: |
| 71 | + |
| 72 | +Problem: |
| 73 | + |
| 74 | ++ |
| 75 | +
|
| 76 | +A query may return an incorrect result under the following conditions: |
| 77 | + |
| 78 | ++ |
| 79 | +
|
| 80 | +* query contains one or more joins |
| 81 | +* one of the joins involves a sub-query (FROM clause subquery) |
| 82 | +* the FROM clause sub-query has a GROUP BY and/or aggregates |
| 83 | +* the FROM clause sub-query can take advantage of index group/aggregate pushdown |
| 84 | +(this requires an appropriate secondary index) |
| 85 | +* CBO is ON, |
| 86 | +and UPDATE STATISTICS has been run on all keyspaces/indexes involved |
| 87 | +
|
| 88 | +*https://jira.issues.couchbase.com/browse/MB-69955/[MB-69955]*:: |
| 89 | + |
| 90 | +`CYCLE` was added as a KEYWORD for RECURSIVE WITH’s CYCLE sub-clause. |
| 91 | ++ |
| 92 | +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] |
| 93 | ++ |
| 94 | +This is now handled by allowing `cycle` keyword as a permitted identifier. |
| 95 | + |
| 96 | +*https://jira.issues.couchbase.com/browse/MB-70112/[MB-70112]*:: |
| 97 | + |
| 98 | +When a prepared request is made with the `auto_execute` request parameter set as `true`, |
| 99 | +the request would incorrectly error out with error: `Unrecognizable prepared statement - cause: JSON unmarshalling error: auto_execute did not produce a prepared statement` |
| 100 | ++ |
| 101 | +In this release the server silently ignores the `auto_execute` request parameter when the request is a prepared request. |
| 102 | + |
| 103 | + |
| 104 | + |
| 105 | + |
| 106 | + |
| 107 | + |
| 108 | + |
| 109 | +[#dlist-fixed-issues-801-index-service] |
| 110 | +=== Index Service |
| 111 | + |
| 112 | +*https://jira.issues.couchbase.com/browse/MB-69935/[MB-69935]*:: |
| 113 | + |
| 114 | +Updated chronology for certain storage API calls to avoid rare corner case of shard metadata mismatch. |
| 115 | + |
| 116 | + |
| 117 | + |
| 118 | +[#dlist-fixed-issues-801-search-service] |
| 119 | +=== Search Service |
| 120 | + |
| 121 | +*https://jira.issues.couchbase.com/browse/MB-68969/[MB-68969]*:: |
| 122 | + |
| 123 | +* 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. |
| 124 | +This has been addressed by denying the sargability for such indexes. |
| 125 | +* Addressed an issue where fields not belonging to a particular keyspace were being included in multi-collection indexes. |
| 126 | +* Addressed a bug that could influence composite field (`_all`) availability based on the order in which fields were processed. |
| 127 | +
|
| 128 | +
|
| 129 | +
|
| 130 | +[#dlist-fixed-issues-801-tools] |
| 131 | +=== Tools |
| 132 | + |
| 133 | +*https://jira.issues.couchbase.com/browse/MB-67774/[MB-67774]*:: |
| 134 | + |
| 135 | +Support has been added for Debian 13, |
| 136 | +codenamed Trixie. |
| 137 | +This update ensures broader compatibility with recent operating system versions. |
| 138 | +Our internal testing has validated the integration of this new platform. |
| 139 | + |
| 140 | +// generated by gemini:gemini-2.5-flash |
| 141 | + |
| 142 | + |
| 143 | + |
| 144 | +*https://jira.issues.couchbase.com/browse/MB-70235/[MB-70235]*:: |
| 145 | + |
| 146 | +In 8.0.0 restoring to a 7.6 and below cluster with `--auto-create-buckets` did not work as we were sending a new setting. |
| 147 | +We now omit the setting depending on the version. |
| 148 | + |
| 149 | +*https://jira.issues.couchbase.com/browse/MB-70255/[MB-70255]*:: |
| 150 | + |
| 151 | +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 |
| 152 | + |
| 153 | + |
| 154 | + |
| 155 | +[#dlist-fixed-issues-801-uncategorized] |
| 156 | +=== Uncategorized |
| 157 | + |
| 158 | +*https://jira.issues.couchbase.com/browse/MB-67774/[MB-67774]*:: |
| 159 | + |
| 160 | +Support has been added for Debian 13, |
| 161 | +codenamed Trixie. |
| 162 | +This update ensures broader compatibility with recent operating system versions. |
| 163 | +Our internal testing has validated the integration of this new platform. |
| 164 | + |
| 165 | +// generated by gemini:gemini-2.5-flash |
| 166 | + |
| 167 | + |
| 168 | + |
0 commit comments