Skip to content

Update vector edge index docs#1608

Open
DavIvek wants to merge 3 commits intomemgraph-3-10from
update-vector-edge-index-docs
Open

Update vector edge index docs#1608
DavIvek wants to merge 3 commits intomemgraph-3-10from
update-vector-edge-index-docs

Conversation

@DavIvek
Copy link
Copy Markdown
Contributor

@DavIvek DavIvek commented Apr 29, 2026

Release note

Vector edge indexes now use the same single-store pattern as node indexe. Drops the dual-store framing for edges, unifies the intro, and extends the DROP-cost warning to cover both nodes and edges.

Related product PRs

PRs from product repo this doc page is related to:
memgraph/memgraph#3929

Checklist:

  • Add appropriate milestone (current release cycle)
  • Add bugfix or feature label, based on the product PR type you're documenting
  • Make sure all relevant tech details are documented
  • Check all content with Grammarly
  • Perform a self-review of my code
  • The build passes locally
  • My changes generate no new warnings or errors

DavIvek added 2 commits April 29, 2026 10:52
memgraph#3929 brings vector edge indexes to the same single-store pattern
as node indexes. Drops the dual-store framing for edges, unifies the
intro, and extends the DROP-cost warning to cover both nodes and edges.
DROP VECTOR INDEX and SHOW VECTOR INDEX INFO are shared between node and
edge variants; only the CREATE syntax and search procedure differ.
@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 29, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
documentation Ready Ready Preview, Comment Apr 29, 2026 1:31pm

Request Review

@DavIvek DavIvek self-assigned this Apr 29, 2026
@DavIvek DavIvek marked this pull request as ready for review April 29, 2026 13:28
@DavIvek DavIvek added this to the 3.10 milestone Apr 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant