Add Memgraph v3.13.0 - #1689
Draft
gitbuda wants to merge 20 commits into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
* docs: document RANGE keyword in CREATE INDEX ... FOR syntax * docs: drop unnecessary note about RANGE with native ON syntax
…rcion behavior (#1696) * docs: document map.get and map.merge_list, and map null/coercion behavior * docs: note node/relationship coercion for map.remove_key, remove_keys, flatten * docs: mark map.set_key value argument as nullable
* refactor: build and package MAGE from the unified CMake tree * update page
* docs: document convert from_json_map/list, to_map and to_json Document the four JSON/map conversion functions in the convert module, including the optional path selector, its supported syntax, and the structured to_json output for nodes, relationships, paths, points and temporals. * docs: correct convert.to_map arg name and to_json node example * docs: add APOC-equivalence callouts and mapping-table rows for convert JSON functions * docs: steer json_util JSON functions to the convert module * docs: move convert-module steer to per-function callouts in json_util * docs: render convert map/list results as Cypher values, not JSON * docs: correct convert.to_map description for non-map values * docs: note convert.to_json supported types and enum error
* Add search module documentation (search.node, search.node_all) * Add search module to available-algorithms index and APOC mappings * docs: clarify =~ is not string-only-guarded in search operators --------- Co-authored-by: Vlasta <95473291+vpavicic@users.noreply.github.com>
…t, duplicates (#1694) * docs: Document NULL handling for collections functions * docs: Document collections.disjunction, subtract, and duplicates * docs: List all collections functions in the compatibility table and mark their equivalents Add the compatibility-table rows for the collections functions that were missing (including disjunction, subtract, duplicates) and add the equivalence callout to the function pages that lacked one, so every collections function consistently states its compatibility mapping. * docs: Include disjunction, subtract, and duplicates in the NULL-handling matrix
Co-authored-by: Cursor <cursoragent@cursor.com>
* docs: HA analytical mode bulk import (memgraph#4510) Document the analytical bulk-import workflow for data instances: switch to IN_MEMORY_ANALYTICAL, import, switch back to IN_MEMORY_TRANSACTIONAL and register the replicas again. - New page clustering/high-availability/analytical-import.mdx with the requirements (MAIN role, zero registered replicas, instance-wide), the step-by-step recipe, the durability guarantees of the switch back, replica re-registration without wiping, and the user-facing error messages. - Storage modes page: drop the "doesn't support replication and high availability" claim, correct the stale "create a snapshot manually before switching back" advice, describe the switch-back snapshot, .old archiving and WAL sequence restart. - Replication and HA command references and best practices: registration and unregistration belong in transactional mode only. - Release notes: breaking change and new feature entries for v3.13.0. - Fix the flag name --storage-enable-backup-dir -> --storage-backup-dir-enabled, which never existed under the documented name. * docs: improvements
Extend the server-side descriptions page with property-value descriptions: the PROPERTY <p> VALUE <literal> target, SET/DELETE examples, the new "property value" type and value column in SHOW DESCRIPTIONS, the description() function for resolving a value's label at query time, and an enum/lookup decoding use case.
Snapshots are written out in bounded chunks so they don't take memory away from the workload running alongside them. Document the flag that sets the chunk size, including that it applies per snapshot thread and so multiplies by --storage-snapshot-thread-count under parallel snapshot creation. The tuning guidance deliberately avoids predicting which direction helps: the effect depends on the hardware, operating system and workload, so it points at measurement rather than an expected result.
Add an "Access control" section to the text-search and vector-search pages explaining how fine-grained access control filters results: a node or relationship surfaces only if the caller can read it (labels/type, and both endpoints for relationships) and the matched/indexed property. Notes the per-procedure property gating (search vs search_all/regex), silent dropping, the aggregate limitation, and wildcard-index per-result filtering.
Covers memgraph/memgraph#4534: - new "Terminate all transactions" section with scope, authorization, self-exclusion, ordering and no-mixing rules - breaking change: transaction ids must parse in full - unauthorized matches now report killed: false - privileges table row and v3.13.0 release notes entries Co-authored-by: Vlasta <95473291+vpavicic@users.noreply.github.com>
* doc: Add docs for global vertex-property indices * refactor: Tidy grammar a little
Co-authored-by: Vlasta <95473291+vpavicic@users.noreply.github.com>
Document memgraph/memgraph#4492: - SHOW INSTANCES is now always answered by the leader coordinator. A follower that cannot reach the leader returns an empty result set with a LeaderNotReachable warning instead of falling back to its local Raft state with "unknown" health. A down data instance now reports the role recorded in the Raft log. - YIELD LEADERSHIP and SHOW COORDINATOR SETTINGS are forwarded to the leader, so they can be run on any coordinator. - SHOW REPLICATION LAG reports why the lag is unavailable via ReplicationLagUnavailable. - ADD COORDINATOR, REMOVE COORDINATOR and UPDATE CONFIG fail with an explicit "coordinator is not a leader" error. Adds a new "When there is no leader to serve the query" error handling section, the ShowCoordSettingsRpc / YieldLeadershipRpc entries, and v3.13.0 release notes. Co-authored-by: Vlasta <95473291+vpavicic@users.noreply.github.com>
* feat: SSO coords * feat: Remove --init-file comment * fix: Notes if SSO on data instances is already set-up * fix: State definitively that --init-file is unsupported in HA mode * docs: SHOW VERSION query (#1715) --------- Co-authored-by: Vlasta <95473291+vpavicic@users.noreply.github.com>
Co-authored-by: Vlasta <95473291+vpavicic@users.noreply.github.com>
gitbuda
commented
Aug 13, 2026
| `killed: false`, indistinguishable from an id that does not exist. | ||
| [#4534](https://github.com/memgraph/memgraph/pull/4534) | ||
|
|
||
| {<h4 className="custom-header">🛠️ Improvements</h4>} |
Member
Author
There was a problem hiding this comment.
I think the order of sections should be
- breaking
- new features
- improvements
- bug fixes
CC @vpavicic
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Make sure to do:
Milestones
Docs Integration Tracking
Breaking changes PRs
Docs needed (Memgraph PR → Docs PR)
Changelog (all PRs requiring a changelog entry)
$and parameter name in query stripper memgraph#4285 @colinbarry