Skip to content

DOC-12207 Release note for Couchbase Server 7.6.2 #3624

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 3, 2024
Merged

DOC-12207 Release note for Couchbase Server 7.6.2 #3624

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions modules/release-notes/partials/docs-server-7.6.2-release-note.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,9 @@ Now, Users with the read-only admin role can now access the backup service. They
|===
|Feature | Description

| https://issues.couchbase.com/browse/MB-60697[MB-60697]
| Vector Search is now supported over macOS and windows platforms

|https://issues.couchbase.com/browse/MB-61216[MB-61216]
| A user had to set the `query` attribute to `match_none` alongside the `knn` attribute within the search request when the user wanted to do a pure kNN search. This behavior will still work.

Expand Down Expand Up @@ -132,6 +135,13 @@ This optimization is crucial for the initial build but should not be used for up
Unfortunately, in a rare sequence of events, all indexes might be accidentally enabled for this optimization, leading to duplicate entries in the storage layer and causing incorrect results.
| Optimization is only enabled for those indexes that are undergoing the initial build process.

| https://issues.couchbase.com/browse/MB-62199[MB-62199]
| During restore, the index planning operation adds replicas for lost replicas of indexes in the plan.

If multiple indexes exist with the same name, there are lost replicas, and there are not enough indexer nodes to hold all the
index replicas in the plan, then extra replicas will not be removed from the plan, and can remain on the old node. +
This causes restore operation failures.
| Issue resolved.
|===
==== Search Service
[#table-fixed-issues-762-search-service,cols="10,40,40"]
Expand Down