diff --git a/next.config.mjs b/next.config.mjs index d88c84826..5cd5a5779 100644 --- a/next.config.mjs +++ b/next.config.mjs @@ -3405,7 +3405,36 @@ export default withNextra({ destination: '/ai-ecosystem#graphchat', permanent: true }, - + { + source: '/getting-started/build-memgraph-from-source#obtaining-the-source-code', + destination: '/getting-started/build-memgraph-from-source#obtain-the-source-code', + permanent: true + }, + { + source: '/getting-started/build-memgraph-from-source#downloading-the-dependencies', + destination: '/getting-started/build-memgraph-from-source#download-dependencies-required-for-methods-1--2', + permanent: true + }, + { + source: '/getting-started/build-memgraph-from-source#compiling', + destination: '/getting-started/build-memgraph-from-source#toolchain-installation-required-for-methods-1--2', + permanent: true + }, + { + source: '/getting-started/build-memgraph-from-source#toolchain-installation-procedure', + destination: '/getting-started/build-memgraph-from-source#toolchain-installation-required-for-methods-1--2', + permanent: true + }, + { + source: '/getting-started/build-memgraph-from-source#installing-memgraph-dependencies', + destination: '/getting-started/build-memgraph-from-source#download-dependencies-required-for-methods-1--2', + permanent: true + }, + { + source: '/getting-started/build-memgraph-from-source#running-memgraph', + destination: '/getting-started/build-memgraph-from-source#run-memgraph', + permanent: true + }, // END: NEW MEMGRAPH LAB REDIRECTS diff --git a/pages/advanced-algorithms/available-algorithms/_meta.ts b/pages/advanced-algorithms/available-algorithms/_meta.ts index 955afeebf..79c4ba716 100644 --- a/pages/advanced-algorithms/available-algorithms/_meta.ts +++ b/pages/advanced-algorithms/available-algorithms/_meta.ts @@ -19,6 +19,7 @@ export default { "degree_centrality": "degree_centrality", "distance_calculator": "distance_calculator", "elasticsearch_synchronization": "elasticsearch_synchronization", + "embeddings": "embeddings", "export_util": "export_util", "gnn_link_prediction": "gnn_link_prediction", "gnn_node_classification": "gnn_node_classification", diff --git a/pages/advanced-algorithms/available-algorithms/embeddings.mdx b/pages/advanced-algorithms/available-algorithms/embeddings.mdx new file mode 100644 index 000000000..e7ea931d4 --- /dev/null +++ b/pages/advanced-algorithms/available-algorithms/embeddings.mdx @@ -0,0 +1,135 @@ +--- +title: embeddings +description: Calculate sentence embeddings on node strings using pytorch. +--- + +# embeddings + +import { Cards } from 'nextra/components' +import GitHub from '/components/icons/GitHub' + +The embeddings module provides tools for calculating sentence embeddings on node strings using pytorch. + + + } + title="Source code" + href="https://github.com/memgraph/mage/blob/main/python/embeddings.py" + /> + + +| Trait | Value | +| ------------------- | ------------------- | +| **Module type** | algorithm | +| **Implementation** | Python | +| **Parallelism** | parallel | + + +## Procedures + +### `compute()` + +The procedure computes the sentence embeddings on the string properties of nodes. Embeddings are +created as a property of the nodes in the graph. + +{

Input:

} + +- `input_nodes: List[Vertex]` (**OPTIONAL**) ➡ The list of nodes to compute the embeddings for. If not provided, the embeddings are computed for all nodes in the graph. +- `embedding_property: string` ➡ The name of the property to store the embeddings in. This property is `embedding` by default. +- `excluded_properties: List[string]` ➡ The list of properties to exclude from the embeddings computation. This list is empty by default. +- `model_name: string` ➡ The name of the model to use for the embeddings computation, buy default this module uses the `all-MiniLM-L6-v2` model provided by the `sentence-transformers` library. +- `batch_size: int` ➡ The batch size to use for the embeddings computation. This is set to `2000` by default. +- `chunk_size: int` ➡ The number of batches per "chunk". This is used when computing embeddings across multiple GPUs, as this has to be done by spawning multiple processes. Each spawned process computes the embeddings for a single chunk. This is set to 48 by default. +- `device: string|int|List[string|int]` ➡ The device to use for the embeddings computation. This can be any of the following: + - `"cpu"` - Use CPU for computation. + - `"cuda"` or `"all"` - Use all available CUDA devices for computation. + - `"cuda:id"` - Use a specific CUDA device for computation. + - `id` - Use a specific device for computation. + - `[id1, id2, ...]` - Use a list of device ids for computation. + - `["cuda:id1", "cuda:id2", ...]` - Use a list of CUDA devices for computation. +by default, the first device (`0`) is used. + +{

Output:

} + +- `success: bool` ➡ Whether the embeddings computation was successful. + +{

Usage:

} + +To compute the embeddings across the entire graph with the default parameters, use the following query: + +```cypher +CALL embeddings.compute() +YIELD success; +``` + +To compute the embeddings for a specific list of nodes, use the following query: + + +```cypher +MATCH (n) +WITH n ORDER BY id(n) +LIMIT 5 +WITH collect(n) AS subset +CALL embeddings.compute(subset) +YIELD success; +``` + +To run the computation on specific device(s), use the following query: + +```cypher +CALL embeddings.compute( + NULL, + "embedding", + NULL, + "all-MiniLM-L6-v2", + 2000, + 48, + "cuda:1" +) +YIELD success; +``` + + +## Example + +Create the following graph: + +```cypher +CREATE (n:Node {id: 1, Title: "Stilton", Description: "A stinky cheese from the UK"}), +(n:Node {id: 2, Title: "Roquefort", Description: "A blue cheese from France"}), +(n:Node {id: 3, Title: "Cheddar", Description: "A yellow cheese from the UK"}), +(n:Node {id: 4, Title: "Gouda", Description: "A Dutch cheese"}), +(n:Node {id: 5, Title: "Parmesan", Description: "An Italian cheese"}), +(n:Node {id: 6, Title: "Red Leicester", Description: "The best cheese in the world"}); +``` + +Run the following query to compute the embeddings: + +```cypher +CALL embeddings.compute() +YIELD success; + +MATCH (n) +WHERE n.embedding IS NOT NULL +RETURN n.Title, n.embedding; +``` + +Results: + +```plaintext ++---------+ +| success | ++---------+ +| true | ++---------+ ++----------------------------------------------------------------------+----------------------------------------------------------------------+ +| n.Title | n.embedding | ++----------------------------------------------------------------------+----------------------------------------------------------------------+ +| "Stilton" | [-0.0485366, -0.021823, 0.0159757, 0.0376443, 0.00594089, -0.0044... | +| "Roquefort" | [-0.0252884, 0.0250485, -0.0249728, 0.0571037, 0.0386177, 0.03863... | +| "Cheddar" | [-0.0129724, -0.00756301, -0.00379329, 0.0037531, -0.0134941, 0.0... | +| "Gouda" | [0.0128716, 0.025435, -0.0288951, 0.0177759, -0.0624398, 0.043577... | +| "Parmesan" | [-0.0755439, 0.00906182, -0.010977, 0.0208911, -0.0527448, 0.0085... | +| "Red Leicester" | [-0.0244318, -0.0280038, -0.0373183, 0.0284436, -0.0277753, 0.066... | ++----------------------------------------------------------------------+----------------------------------------------------------------------+ +``` \ No newline at end of file diff --git a/pages/advanced-algorithms/available-algorithms/map.mdx b/pages/advanced-algorithms/available-algorithms/map.mdx index 4ae8f66f6..c5adb3bff 100644 --- a/pages/advanced-algorithms/available-algorithms/map.mdx +++ b/pages/advanced-algorithms/available-algorithms/map.mdx @@ -171,7 +171,9 @@ RETURN map.from_pairs([["b", 3], ["c", "c"]]) AS map; ### `merge()` The procedure merges two maps into one. If the same key occurs twice, the later -value will overwrite the previous one. +value will overwrite the previous one. + +If null is provided as an argument, it will resolve to an empty map. This function is equivalent to **apoc.map.merge**. @@ -179,8 +181,8 @@ This function is equivalent to **apoc.map.merge**. {

Input:

} -- `first: Map` ➡ A map containing key-value pairs that need to be merged with another map. -- `second: Map` ➡ The second map containing key-value pairs that need to be merged with the key-values from the first map. +- `first: mgp.Nullable[Map]` ➡ A map containing key-value pairs that need to be merged with another map. +- `second: mgp.Nullable[Map]` ➡ The second map containing key-value pairs that need to be merged with the key-values from the first map. {

Output:

} diff --git a/pages/advanced-algorithms/install-mage.mdx b/pages/advanced-algorithms/install-mage.mdx index 9ee1ef209..909415e0d 100644 --- a/pages/advanced-algorithms/install-mage.mdx +++ b/pages/advanced-algorithms/install-mage.mdx @@ -33,6 +33,9 @@ The following tags are available on Docker Hub: - `x.y` - production MAGE image - `x.y-relwithdebinfo` - contains debugging symbols and `gdb` - `x.y-malloc` - Memgraph compiled with `malloc`instead of `jemalloc` (x86_64 only) +- `x.y-relwithdebinfo-cuda` - Memgraph built with CUDA support* - available since version `3.6.1`. + +*To run GPU-accelerated algorithms, you need to launch the container with the `--gpus all` flag. For versions prior to `3.2`, MAGE image tags included both MAGE and Memgraph versions, e.g. @@ -90,7 +93,7 @@ sudo apt-get update && sudo apt-get install -y \ git \ pkg-config \ uuid-dev \ - libxmlsec1-dev xmlsec1 \ + xmlsec1 \ --no-install-recommends ``` @@ -106,7 +109,7 @@ git clone --recurse-submodules https://github.com/memgraph/mage.git && cd mage Download and install the [Memgraph Toolchain](https://memgraph.com/docs/getting-started/build-memgraph-from-source#toolchain-installation-procedure): ```bash -curl -L https://s3-eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v6/toolchain-v6-binaries-ubuntu-24.04-amd64.tar.gz -o toolchain.tar.gz +curl -L https://s3-eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v7/toolchain-v7-binaries-ubuntu-24.04-amd64.tar.gz -o toolchain.tar.gz sudo tar xzvfm toolchain.tar.gz -C /opt ``` @@ -125,16 +128,25 @@ curl https://sh.rustup.rs -sSf | sh -s -- -y export PATH="/root/.cargo/bin:${PATH}" python3 -m pip install -r python/requirements.txt python3 -m pip install -r cpp/memgraph/src/auth/reference_modules/requirements.txt -python3 -m pip install torch-sparse torch-cluster torch-spline-conv torch-geometric torch-scatter -f https://data.pyg.org/whl/torch-2.3.0+cpu.html -python3 -m pip install dgl -f https://data.dgl.ai/wheels/torch-2.3/repo.html +python3 -m pip install torch-sparse torch-cluster torch-spline-conv torch-geometric torch-scatter -f https://data.pyg.org/whl/torch-2.6.0+cpu.html +python3 -m pip install dgl -f https://data.dgl.ai/wheels/torch-2.6/repo.html +``` + + + +To install the dependencies for GPU-accelerated algorithms, you need to use the GPU-specific requirements file: + +```shell +python3 -m pip install -r python/requirements-gpu.txt ``` + {

Run the `setup` script

} Run the following command: ```shell -source /opt/toolchain-v6/activate +source /opt/toolchain-v7/activate python3 setup build sudo cp -r dist/* /usr/lib/memgraph/query_modules ``` diff --git a/pages/custom-query-modules/python.mdx b/pages/custom-query-modules/python.mdx index d1ca0335a..bdd8de3a4 100644 --- a/pages/custom-query-modules/python.mdx +++ b/pages/custom-query-modules/python.mdx @@ -55,7 +55,7 @@ inside a Docker container, run the following command in the terminal: ``` -docker exec -i -u root bash -c "apt install -y python3-pip && +docker exec -i -u memgraph bash -c "apt install -y python3-pip && pip install pandas" ``` @@ -69,16 +69,16 @@ commands in the Dockerfile: ``` FROM memgraph/memgraph:latest -USER root +USER memgraph RUN apt install -y python3-pip RUN pip install pandas -USER memgraph ``` -It is important that you install Python library as a `root` user, rather than -the default `memgraph` user. +Python libraries should now be installed as the `memgraph` user, which is the +default user inside the Memgraph container. You no longer need to switch to the +`root` user to perform installations. ## Example diff --git a/pages/database-management/authentication-and-authorization/query-privileges.mdx b/pages/database-management/authentication-and-authorization/query-privileges.mdx new file mode 100644 index 000000000..d24575f88 --- /dev/null +++ b/pages/database-management/authentication-and-authorization/query-privileges.mdx @@ -0,0 +1,270 @@ +--- +title: Query privileges reference +description: Comprehensive reference for query privileges and required permissions in Memgraph. +--- + +import { Callout } from 'nextra/components' + +# Query privileges reference Enterprise + +This comprehensive reference provides detailed information about the privilege system in Memgraph, including which privileges are required for different types of queries and operations. + + +This page complements the [Role-based access control](/database-management/authentication-and-authorization/role-based-access-control) documentation by providing detailed privilege requirements for specific queries and operations. + + + +Memgraph's privilege system controls access to various database operations through a comprehensive set of privileges. The system analyzes queries and determines the required privileges using the `PrivilegeExtractor` class, which implements the visitor pattern to traverse the Abstract Syntax Tree (AST) and extract privilege requirements. + +## Cypher query privileges + +### Basic operations + +| Query Type | Required Privileges | Example | +|------------|-------------------|---------| +| `CREATE` | `CREATE` | `CREATE (n:Person {name: "Alice"})` | +| `MATCH` | `MATCH` | `MATCH (n:Person) RETURN n` | +| `DELETE` | `DELETE` | `MATCH (n) DELETE n` | +| `MERGE` | `MERGE` | `MERGE (n:Person {id: 1})` | +| `SET` (properties) | `SET` | `MATCH (n) SET n.name = "Bob"` | +| `SET` (labels) | `SET` | `MATCH (n) SET n:Employee` | +| `REMOVE` (properties) | `REMOVE` | `MATCH (n) REMOVE n.temp` | +| `REMOVE` (labels) | `REMOVE` | `MATCH (n) REMOVE n:Temp` | + +### Complex queries + +| Query Type | Required Privileges | Example | +|------------|-------------------|---------| +| `MATCH` + `DELETE` | `MATCH`, `DELETE` | `MATCH (n) DELETE n` | +| `MATCH` + `CREATE` | `MATCH`, `CREATE` | `MATCH (n) CREATE (m)-[:KNOWS]->(n)` | +| `MATCH` + `SET` | `MATCH`, `SET` | `MATCH (n) SET n.updated = true` | +| `MATCH` + `REMOVE` | `MATCH`, `REMOVE` | `MATCH (n) REMOVE n:Old` | + +## Index operations + +| Query Type | Required Privileges | Example | +|------------|-------------------|---------| +| `CREATE INDEX` | `INDEX` | `CREATE INDEX ON :Person(name)` | +| `DROP INDEX` | `INDEX` | `DROP INDEX ON :Person(name)` | +| `CREATE EDGE INDEX` | `INDEX` | `CREATE EDGE INDEX ON :KNOWS` | +| `CREATE TEXT INDEX` | `INDEX` | `CREATE TEXT INDEX ON :Person(name)` | +| `CREATE VECTOR INDEX` | `INDEX` | `CREATE VECTOR INDEX ON :Document(embedding)` | +| `CREATE TEXT EDGE INDEX` | `INDEX` | `CREATE TEXT EDGE INDEX ON :KNOWS(description)` | +| `CREATE VECTOR EDGE INDEX` | `INDEX` | `CREATE VECTOR EDGE INDEX ON :SIMILAR(embedding)` | +| `ANALYZE GRAPH` | `INDEX` | `ANALYZE GRAPH` | +| `DROP ALL INDEXES` | `INDEX` | `DROP ALL INDEXES` | + +## Constraint operations + +| Query Type | Required Privileges | Example | +|------------|-------------------|---------| +| `CREATE CONSTRAINT` | `CONSTRAINT` | `CREATE CONSTRAINT ON (n:Person) ASSERT n.id IS UNIQUE` | +| `DROP CONSTRAINT` | `CONSTRAINT` | `DROP CONSTRAINT ON (n:Person) ASSERT n.id IS UNIQUE` | +| `DROP ALL CONSTRAINTS` | `CONSTRAINT` | `DROP ALL CONSTRAINTS` | + +## Authentication and authorization + +| Query Type | Required Privileges | Special Cases | +|------------|-------------------|---------------| +| `CREATE ROLE` | `AUTH` | | +| `DROP ROLE` | `AUTH` | | +| `SHOW ROLES` | `AUTH` | | +| `CREATE USER` | `AUTH` | | +| `SET PASSWORD` | `AUTH` | | +| `CHANGE PASSWORD` | **None** | Users can change their own password. | +| `DROP USER` | `AUTH` | | +| `SHOW CURRENT USER` | **None** | Users can always see their own info. | +| `SHOW CURRENT ROLE` | **None** | Users can always see their current role. | +| `SHOW USERS` | `AUTH` | | +| `SET ROLE` | `AUTH` | | +| `CLEAR ROLE` | `AUTH` | | +| `GRANT PRIVILEGE` | `AUTH` | | +| `DENY PRIVILEGE` | `AUTH` | | +| `REVOKE PRIVILEGE` | `AUTH` | | +| `SHOW PRIVILEGES` | `AUTH` | | +| `SHOW ROLE FOR USER` | `AUTH` | | +| `SHOW USERS FOR ROLE` | `AUTH` | | +| `GRANT DATABASE TO USER` | `AUTH` | | +| `DENY DATABASE FROM USER` | `AUTH` | | +| `REVOKE DATABASE FROM USER` | `AUTH` | | +| `SHOW DATABASE PRIVILEGES` | `AUTH` | | +| `SET MAIN DATABASE` | `AUTH` | | +| `GRANT IMPERSONATE USER` | `AUTH` | | +| `DENY IMPERSONATE USER` | `AUTH` | | + +## Database information queries + +| Query Type | Required Privileges | Example | +|------------|-------------------|---------| +| `SHOW INDEX INFO` | `INDEX` | `SHOW INDEX INFO` | +| `SHOW EDGE TYPES` | `INDEX` | `SHOW EDGE_TYPES INFO` | +| `SHOW NODE LABELS` | `INDEX` | `SHOW NODE_LABELS INFO` | +| `SHOW VECTOR INDEX INFO` | `INDEX` | `SHOW VECTOR INDEX INFO` | +| `SHOW CONSTRAINT INFO` | `CONSTRAINT` | `SHOW CONSTRAINT INFO` | +| `SHOW METRICS` | `STATS` | `SHOW METRICS INFO` | + +## System information queries + +| Query Type | Required Privileges | Example | +|------------|-------------------|---------| +| `SHOW STORAGE INFO` | `STATS` | `SHOW STORAGE INFO` | +| `SHOW BUILD INFO` | `STATS` | `SHOW BUILD INFO` | +| `SHOW ACTIVE USERS` | `STATS` | `SHOW ACTIVE USERS` | +| `SHOW LICENSE INFO` | `CONFIG` | `SHOW LICENSE INFO` | +| `SHOW INSTANCE` | `STATS` | `SHOW INSTANCE` | +| `SHOW INSTANCES` | `STATS` | `SHOW INSTANCES` | + +## Administrative operations + +| Query Type | Required Privileges | Example | +|------------|-------------------|---------| +| `DUMP DATABASE` | `DUMP` | `DUMP DATABASE` | +| `LOCK DATA DIRECTORY` | `DURABILITY` | `LOCK DATA DIRECTORY` | +| `UNLOCK DATA DIRECTORY` | `DURABILITY` | `UNLOCK DATA DIRECTORY` | +| `DATA DIRECTORY LOCK STATUS` | `DURABILITY` | `DATA DIRECTORY LOCK STATUS` | +| `FREE MEMORY` | `FREE_MEMORY` | `FREE MEMORY` | +| `SHOW CONFIG` | `CONFIG` | `SHOW CONFIG` | +| `CREATE TRIGGER` | `TRIGGER` | `CREATE TRIGGER ...` | +| `DROP TRIGGER` | `TRIGGER` | `DROP TRIGGER ...` | +| `SHOW TRIGGERS` | `TRIGGER` | `SHOW TRIGGERS` | +| `SHOW TRIGGER INFO` | `TRIGGER` | `SHOW TRIGGER INFO` | +| `CREATE STREAM` | `STREAM` | `CREATE STREAM ...` | +| `DROP STREAM` | `STREAM` | `DROP STREAM ...` | +| `SET ISOLATION LEVEL` | `CONFIG` | `SET ISOLATION LEVEL ...` | +| `SET STORAGE MODE` | `STORAGE_MODE` | `SET STORAGE MODE ...` | +| `CREATE SNAPSHOT` | `DURABILITY` | `CREATE SNAPSHOT` | +| `RECOVER SNAPSHOT` | `DURABILITY` | `RECOVER SNAPSHOT` | +| `SHOW SNAPSHOTS` | `DURABILITY` | `SHOW SNAPSHOTS` | +| `SHOW NEXT SNAPSHOT` | `DURABILITY` | `SHOW NEXT SNAPSHOT` | +| `SET SETTING` | `CONFIG` | `SET SETTING ...` | +| `SHOW VERSION` | `STATS` | `SHOW VERSION` | +| `SHOW TRANSACTIONS` | `TRANSACTION_MANAGEMENT` | `SHOW TRANSACTIONS` | +| `TERMINATE TRANSACTIONS` | `TRANSACTION_MANAGEMENT` | `TERMINATE TRANSACTIONS 'transaction_id'` | + +## Replication operations + +| Query Type | Required Privileges | Example | +|------------|-------------------|---------| +| `REPLICATION` operations | `REPLICATION` | Various replication commands. | +| `SHOW REPLICATION ROLE` | `REPLICATION` | `SHOW REPLICATION ROLE` | +| `SHOW REPLICAS` | `REPLICATION` | `SHOW REPLICAS` | +| `SHOW REPLICATION LAG` | `COORDINATOR` | `SHOW REPLICATION LAG` | + +## Multi-database operations + +| Query Type | Required Privileges | Special Cases | +|------------|-------------------|---------------| +| `CREATE DATABASE` | `MULTI_DATABASE_EDIT` | | +| `DROP DATABASE` | `MULTI_DATABASE_EDIT` | | +| `RENAME DATABASE` | `MULTI_DATABASE_EDIT` | | +| `DROP DATABASE FORCE` | `MULTI_DATABASE_EDIT`, `TRANSACTION_MANAGEMENT` | Requires both privileges. | +| `USE DATABASE` | `MULTI_DATABASE_USE` | | +| `SHOW DATABASE` | **None** | Users can see current database. | +| `SHOW DATABASES` | `MULTI_DATABASE_USE` | | + +## Enum operations + +| Query Type | Required Privileges | Example | +|------------|-------------------|---------| +| `CREATE ENUM` | `CREATE` | `CREATE ENUM ...` | +| `SHOW ENUMS` | `STATS` | `SHOW ENUMS` | +| `ALTER ENUM ADD VALUE` | `CREATE` | `ALTER ENUM ... ADD VALUE ...` | +| `ALTER ENUM UPDATE VALUE` | `CREATE` | `ALTER ENUM ... UPDATE VALUE ...` | +| `ALTER ENUM REMOVE VALUE` | `DELETE` | `ALTER ENUM ... REMOVE VALUE ...` | +| `DROP ENUM` | `DELETE` | `DROP ENUM ...` | + +## TTL operations + +| Query Type | Required Privileges | Note | +|------------|-------------------|------| +| `TTL` operations | `CONFIG`, `INDEX`, `MATCH`, `DELETE` | Requires multiple privileges. | + +## Coordinator operations + +| Query Type | Required Privileges | Example | +|------------|-------------------|---------| +| `COORDINATOR` operations | `COORDINATOR` | Various coordinator commands. | +| `SHOW COORDINATOR SETTINGS` | `COORDINATOR` | `SHOW COORDINATOR SETTINGS` | + +## Schema information + +| Query Type | Required Privileges | Example | +|------------|-------------------|---------| +| `SHOW SCHEMA INFO` | `STATS` | `SHOW SCHEMA INFO` | + +## User profile operations + +| Query Type | Required Privileges | Example | +|------------|-------------------|---------| +| `USER PROFILE` operations | `PROFILE_RESTRICTION` | User profile management. | + +## Procedure calls + +| Procedure Type | Required Privileges | Example | +|----------------|-------------------|---------| +| `mg.get_module_files` | `MODULE_READ` | `CALL mg.get_module_files()` | +| `mg.create_module_file` | `MODULE_WRITE` | `CALL mg.create_module_file(...)` | +| `mg.update_module_file` | `MODULE_WRITE` | `CALL mg.update_module_file(...)` | +| `mg.get_module_file` | `MODULE_READ` | `CALL mg.get_module_file(...)` | +| `mg.delete_module_file` | `MODULE_WRITE` | `CALL mg.delete_module_file(...)` | +| Other procedures | **Procedure-specific** | Depends on procedure definition. | + +## File operations + +| Query Type | Required Privileges | Example | +|------------|-------------------|---------| +| `LOAD CSV` | `READ_FILE` | `LOAD CSV FROM "file.csv" AS row` | + +## Special cases + +| Query Type | Required Privileges | Notes | +|------------|-------------------|-------| +| `EXPLAIN` | **Inherits privileges from inner query** | Privileges depend on the explained query. | +| `PROFILE` | **Inherits privileges from inner query** | Privileges depend on the profiled query. | +| `SET SESSION TRACE` | **None** | No privileges required. | + +### Examples + +```cypher +-- EXPLAIN inherits privileges from the inner query +EXPLAIN MATCH (n:Person) RETURN n; -- Requires MATCH privilege + +-- PROFILE inherits privileges from the inner query +PROFILE CREATE (n:Person {name: "Alice"}); -- Requires CREATE privilege +``` + +## Troubleshooting + +### Common privilege errors + + +If you encounter "Vertex not created due to not having enough permission!" errors, you likely need to grant fine-grained access control privileges to the user. + + +### Checking privileges + +```cypher +-- Show all privileges for a user or role +SHOW PRIVILEGES FOR username; + +-- Show privileges in specific database context +SHOW PRIVILEGES FOR username ON DATABASE db_name; + +-- Verify the current logged-in user +SHOW CURRENT USER; + +-- Show current user's privileges +SHOW PRIVILEGES FOR CURRENT USER; +``` + +### Privilege inheritance + +Remember that: +- **Grants**: If any role grants a permission, the user has that permission +- **Denies**: If any role denies a permission, the user is denied that permission +- **Database Access**: If any role grants access to a database, the user has access +- **Fine-grained Permissions**: Combined using the same grant/deny logic + + +Privilege changes take effect after the user reconnects to the database. + diff --git a/pages/database-management/authentication-and-authorization/role-based-access-control.mdx b/pages/database-management/authentication-and-authorization/role-based-access-control.mdx index e83499792..fc8e42a2e 100644 --- a/pages/database-management/authentication-and-authorization/role-based-access-control.mdx +++ b/pages/database-management/authentication-and-authorization/role-based-access-control.mdx @@ -172,10 +172,16 @@ of the following commands: | Privilege to change [storage mode](/fundamentals/storage-memory-usage#storage-modes). | `STORAGE_MODE` | | Privilege to manage [multi-tenant databases](/database-management/multi-tenancy). | `MULTI_DATABASE_EDIT` | | Privilege to use a database within the multi-tenant architecture. | `MULTI_DATABASE_USE` | +| Privilege to configure [high-availability](/clustering/high-availability) coordinators. | `COORDINATOR` | +| Privilege to [impersonate other users](/database-management/authentication-and-authorization/impersonate-user). | `IMPERSONATE_USER` | | Privilege to set limits and monitor resource usage per user. | `PROFILE_RESTRICTION` | | Privileges to specific labels. | `ALL LABELS` | | Privileges to specific relationships types. | `ALL EDGE TYPES` | + +For a comprehensive reference of which privileges are required for specific queries and operations, see the [Query privileges reference](/database-management/authentication-and-authorization/query-privileges) documentation. + + ## Authentication and authorization requirements diff --git a/pages/database-management/debugging.mdx b/pages/database-management/debugging.mdx index ed0b0c399..0e45245ac 100644 --- a/pages/database-management/debugging.mdx +++ b/pages/database-management/debugging.mdx @@ -235,6 +235,69 @@ services: ``` +### Using `heaptrack` with Docker + +All `RelWithDebInfo` images come with `heaptrack` installed. You can use it to track the memory usage of Memgraph. + +Before starting the container, create a directory to store the heaptrack data: + +```bash +mkdir -p /tmp/heaptrack +chmod a+rwx /tmp/heaptrack +``` + +Then start the container with the following command: + +```bash +docker run -d --rm \ + --name memgraph \ + -v /tmp/heaptrack:/data \ + --entrypoint /usr/bin/heaptrack \ + memgraph/memgraph:3.6.1-relwithdebinfo \ + --output /data/heaptrack.memgraph \ + -- \ + /usr/lib/memgraph/memgraph +``` + + + Running the MAGE container using this method will result in a segmentation fault due to the way + that `heaptrack` interacts with Python, so memgraph should be launched by `heaptrack` using the `--use-inject` flag: + + ```bash + docker run -d --rm \ + --name memgraph \ + -p 7687:7687 \ + -v /tmp/heaptrack:/data \ + --entrypoint /usr/bin/heaptrack \ + memgraph/memgraph-mage:3.6.1-relwithdebinfo \ + --output /data/heaptrack.memgraph \ + --use-inject /usr/lib/memgraph/memgraph + ``` + + +To stop `memgraph` gracefully: + +```bash +docker exec memgraph bash -c "kill -SIGINT \$(pidof memgraph)" +``` + +Then the `heaptrack` GUI can be used to inspect the heaptrack data on the host machine: + +```bash +heaptrack /tmp/heaptrack/heaptrack.memgraph.gz +``` + + + The `heaptrack` GUI can be installed on the host machine by issuing the command (Debian/Ubuntu): + ```bash + sudo apt install heaptrack + ``` + or by issuing the command (Fedora): + ```bash + sudo dnf install heaptrack + ``` + + ### Profiling with `perf` Perfing is the most common operation that is run when Memgraph is hanging or diff --git a/pages/database-management/monitoring.mdx b/pages/database-management/monitoring.mdx index 570cb2789..190a450bd 100644 --- a/pages/database-management/monitoring.mdx +++ b/pages/database-management/monitoring.mdx @@ -268,6 +268,16 @@ three different types: | ActivePointIndices | Counter | Number of active point indices in the system. | | ActiveTextIndices | Counter | Number of active text indexes in the system. | +#### Memory metrics + + | Name | Type | Description | + | ------------------------------- | --------- | -------------------------------------------------------------------| + | GCLatency_us_50p | Histogram | GC total cleanup time in microseconds (50th percentile). | + | GCLatency_us_90p | Histogram | GC total cleanup time in microseconds (90th percentile). | + | GCLatency_us_99p | Histogram | GC total cleanup time in microseconds (99th percentile). | + | GCSkiplistCleanupLatency_us_50p | Histogram | GC time spent for cleaning skiplists in indexes (50th percentile). | + | GCSkiplistCleanupLatency_us_90p | Histogram | GC time spent for cleaning skiplists in indexes (90th percentile). | + | GCSkiplistCleanupLatency_us_99p | Histogram | GC time spent for cleaning skiplists in indexes (99th percentile). | #### Operator metrics @@ -375,15 +385,17 @@ and describes a particular operation. #### Transaction metrics - | Name | Type | Description | - | ---------------------- | ------- | ------------------------------------------------------------------------------- | - | ActiveTransactions | Counter | Number of active transactions. | - | CommittedTransactions | Counter | Number of committed transactions. | - | RollbackedTransactions | Counter | Number of rollbacked transactions. | - | FailedQuery | Counter | Number of times executing a query failed (either during parse time or runtime). | - | FailedPrepare | Counter | Number of times preparing a query failed. | - | FailedPull | Counter | Number of times pulling a query failed. | - | SuccessfulQuery | Counter | Number of successful queries. | + | Name | Type | Description | + | ---------------------- | ------- | --------------------------------------------------------------------------------------------------------------------------| + | ActiveTransactions | Counter | Number of active transactions. | + | CommittedTransactions | Counter | Number of committed transactions. | + | RollbackedTransactions | Counter | Number of rollbacked transactions. | + | FailedQuery | Counter | Number of times executing a query failed (either during parse time or runtime). | + | FailedPrepare | Counter | Number of times preparing a query failed. | + | FailedPull | Counter | Number of times pulling a query failed. | + | SuccessfulQuery | Counter | Number of successful queries. | + | TransientErrors | Counter | Number of times a transient error happened. Transient errors are those errors which can be retried. | + | WriteWriteConflicts | Counter | Number of times a write-write conflict happened (2 transactions performing modification to the same node simultaneously). | #### Trigger metrics diff --git a/pages/database-management/server-stats.md b/pages/database-management/server-stats.md index 77cdb87aa..d97c306c6 100644 --- a/pages/database-management/server-stats.md +++ b/pages/database-management/server-stats.md @@ -202,6 +202,12 @@ SHOW METRICS; | "DiskUsage" | "Memory" | "Gauge" | 81508835 | | "MemoryRes" | "Memory" | "Gauge" | 339640320 | | "PeakMemoryRes" | "Memory" | "Gauge" | 339775488 | +| "GCLatency_us_50p" | "Memory" | "Histogram" | 1000 | +| "GCLatency_us_90p" | "Memory" | "Histogram" | 1000 | +| "GCLatency_us_99p" | "Memory" | "Histogram" | 1000 | +| "GCSkiplistCleanupLatency_us_50p" | "Memory" | "Histogram" | 500 | +| "GCSkiplistCleanupLatency_us_90p" | "Memory" | "Histogram" | 500 | +| "GCSkiplistCleanupLatency_us_99p" | "Memory" | "Histogram" | 500 | | "AccumulateOperator" | "Operator" | "Counter" | 0 | | "AggregateOperator" | "Operator" | "Counter" | 0 | | "ApplyOperator" | "Operator" | "Counter" | 0 | @@ -283,6 +289,8 @@ SHOW METRICS; | "FailedQuery" | "Transaction" | "Counter" | 0 | | "RollbackedTransactions" | "Transaction" | "Counter" | 0 | | "SuccessfulQuery" | "Transaction" | "Counter" | 1 | +| "TransientErrors" | "Transaction" | "Counter" | 0 | +| "WriteWriteConflicts" | "Transaction" | "Counter" | 0 | | "TriggersCreated" | "Trigger" | "Counter" | 0 | | "TriggersExecuted" | "Trigger" | "Counter" | 0 | +------------------------------------------+---------------------+-------------+------------+ diff --git a/pages/deployment/benchmarking-memgraph.mdx b/pages/deployment/benchmarking-memgraph.mdx index fbee1cb77..015b7f809 100644 --- a/pages/deployment/benchmarking-memgraph.mdx +++ b/pages/deployment/benchmarking-memgraph.mdx @@ -62,7 +62,7 @@ While `mgbench` gives you full control over benchmarking and produces raw result analyzing performance metrics at scale can be time-consuming. That’s why we created [**Benchgraph**](https://github.com/memgraph/benchgraph)—a companion visualization tool for `mgbench`. -![](/pages/memgraph-in-production/benchmarking-memgraph/benchgraph-snippet.png) +![](/pages/deployment/benchmarking-memgraph/benchgraph-snippet.png) Benchgraph is not required to use `mgbench`, but it offers a **convenient way to visualize and explore** benchmark results across a variety of run conditions: diff --git a/pages/deployment/workloads.mdx b/pages/deployment/workloads.mdx index 83202ddf6..0625c4d8d 100644 --- a/pages/deployment/workloads.mdx +++ b/pages/deployment/workloads.mdx @@ -8,10 +8,13 @@ import {CommunityLinks} from '/components/social-card/CommunityLinks' # Workloads -When deploying Memgraph in production, it is essential to consider a set of prerequisites to ensure optimal **performance**, **scalability** -and **resilience**. That includes decisions about hardware configurations and integration strategies. +When deploying Memgraph in production, it is essential to consider a set of +prerequisites to ensure optimal **performance**, **scalability** and +**resilience**. That includes decisions about hardware configurations and +integration strategies. -This section provides guides that are the starting point to production-readiness with Memgraph. +This section provides guides that are the starting point to production-readiness +with Memgraph. Before you dive into specific setups, it's important to think about: - **Hardware requirements** and **instance sizing** @@ -20,18 +23,23 @@ Before you dive into specific setups, it's important to think about: - **Data import** best practices - Connecting to **external sources** -These factors ensure Memgraph performs effectively in your environment, no matter the use case. +These factors ensure Memgraph performs effectively in your environment, no +matter the use case. ## How to use these guides -**Start with the [Deployment best practices](/deployment/best-practices)**. That page covers the **best practices** that apply to most -production deployments, regardless of your workload type and are **agnostic to specific use cases**. -Each separate guide in the Workloads section focuses on a particular type of workload or deployment scenario. -At the beginning of each guide, you’ll learn when that **use case** is a good fit for your needs and specific tailored **recommendations**. +**Start with the [Deployment best practices](/deployment/best-practices)**. That +page covers the **best practices** that apply to most production deployments, +regardless of your workload type and are **agnostic to specific use cases**. +Each separate guide in the Workloads section focuses on a particular type of +workload or deployment scenario. At the beginning of each guide, you’ll learn +when that **use case** is a good fit for your needs and specific tailored +**recommendations**. -Recommendations in those guides **override** anything written in the -general suggestions when there's a conflict, so always defer to the targeted guide when applicable. +Recommendations in those guides **override** anything written in the general +suggestions when there's a conflict, so always defer to the targeted guide when +applicable. ## Available guides @@ -42,20 +50,26 @@ Here are the currently available guides to help you deploy Memgraph effectively: Learn how to utilize memgraph across your cyber security network. ### [Memgraph in high-throughput workloads](/deployment/workloads/memgraph-in-high-throughput-workloads) -Scale your write throughput while keeping up with fast-changing, high-velocity graph data. +Scale your write throughput while keeping up with fast-changing, high-velocity +graph data. ### [Memgraph in GraphRAG use cases](/deployment/workloads/memgraph-in-graphrag) -Learn how to optimize Memgraph for Retrieval-Augmented Generation (RAG) systems using graph data. +Learn how to optimize Memgraph for Retrieval-Augmented Generation (RAG) systems +using graph data. + +### [Memgraph in mission critical workloads](/deployment/workloads/memgraph-in-mission-critical-workloads) +Learn how to configure Memgraph for high availability, strong consistency, and +fault tolerance in mission-critical production environments. ## 🚧 Guides in construction - Memgraph in transactional workloads - Memgraph in analytical workloads -- Memgraph in mission critical workloads - Memgraph in supply chain use cases - Memgraph in fraud detection use cases -If you'd like to help us **prioritize** this content, feel free to reach out on [Discord](https://discord.gg/memgraph)! +If you'd like to help us **prioritize** this content, feel free to reach out on +[Discord](https://discord.gg/memgraph)! Your feedback helps us build what matters most. diff --git a/pages/deployment/workloads/_meta.ts b/pages/deployment/workloads/_meta.ts index d091f6364..0c82c3992 100644 --- a/pages/deployment/workloads/_meta.ts +++ b/pages/deployment/workloads/_meta.ts @@ -2,4 +2,5 @@ export default { "memgraph-in-cybersecurity": "Memgraph in cybersecurity", "memgraph-in-graphrag": "Memgraph in GraphRAG use cases", "memgraph-in-high-throughput-workloads": "Memgraph in high-throughput workloads", + "memgraph-in-mission-critical-workloads": "Memgraph in mission critical workloads", } diff --git a/pages/deployment/workloads/memgraph-in-cybersecurity.mdx b/pages/deployment/workloads/memgraph-in-cybersecurity.mdx index 38266c935..1e62decad 100644 --- a/pages/deployment/workloads/memgraph-in-cybersecurity.mdx +++ b/pages/deployment/workloads/memgraph-in-cybersecurity.mdx @@ -50,7 +50,7 @@ Here's why Memgraph is a great fit for cybersecurity use cases: While many graph databases **max out around 1,000 events per second**, Memgraph can handle **up to 50x more** (see image below), making it ideal for **high-velocity security event processing**. - ![](/pages/memgraph-in-production/benchmarking-memgraph/realistic-workload.png) + ![](/pages/deployment/benchmarking-memgraph/realistic-workload.png) - **Non-blocking reads and writes with MVCC**: Built on multi-version concurrency control (MVCC), Memgraph ensures that **security event ingestion doesn't block threat analysis** and **analysis doesn't block ingestion**, diff --git a/pages/deployment/workloads/memgraph-in-graphrag.mdx b/pages/deployment/workloads/memgraph-in-graphrag.mdx index 23a25e634..75b11c33f 100644 --- a/pages/deployment/workloads/memgraph-in-graphrag.mdx +++ b/pages/deployment/workloads/memgraph-in-graphrag.mdx @@ -43,7 +43,7 @@ Here's what makes Memgraph a perfect fit for GraphRAG: ## What is covered? The suggestions for GraphRAG use cases **complement** several key sections in the -[general suggestions guide](/memgraph-in-production/general-suggestions). These sections offer important context and +[general suggestions guide](/deployment/best-practices). These sections offer important context and additional best practices tailored for performance, stability, and scalability in GraphRAG systems: - [Hardware sizing](#hardware-sizing) diff --git a/pages/deployment/workloads/memgraph-in-high-throughput-workloads.mdx b/pages/deployment/workloads/memgraph-in-high-throughput-workloads.mdx index 46f5ba1d4..cb201dd04 100644 --- a/pages/deployment/workloads/memgraph-in-high-throughput-workloads.mdx +++ b/pages/deployment/workloads/memgraph-in-high-throughput-workloads.mdx @@ -45,7 +45,7 @@ Here's why Memgraph is a great fit for high-throughput use cases: While many graph databases **max out around 1,000 writes per second**, Memgraph can handle **up to 50x more** (see image below), making it ideal for **high-velocity, write-intensive workloads**. - ![](/pages/memgraph-in-production/benchmarking-memgraph/realistic-workload.png) + ![](/pages/deployment/benchmarking-memgraph/realistic-workload.png) - **Non-blocking reads and writes with MVCC**: Built on multi-version concurrency control (MVCC), Memgraph ensures that **writes don’t block reads** and **reads don’t block writes**, allowing each to scale independently. @@ -71,7 +71,7 @@ Here's why Memgraph is a great fit for high-throughput use cases: ## What is covered? The suggestions for high-throughput workloads **complement** several key sections in the -[general suggestions guide](/memgraph-in-production/general-suggestions). These sections offer important context and +[best practices guide](/deployment/best-practices). These sections offer important context and additional best practices tailored for performance, stability, and scalability in high-throughput systems: - [Hardware configuration](#hardware-configuration)
diff --git a/pages/deployment/workloads/memgraph-in-mission-critical-workloads.mdx b/pages/deployment/workloads/memgraph-in-mission-critical-workloads.mdx new file mode 100644 index 000000000..3e5815564 --- /dev/null +++ b/pages/deployment/workloads/memgraph-in-mission-critical-workloads.mdx @@ -0,0 +1,224 @@ +--- +title: Memgraph in mission-critical workloads +description: Suggestions on how to bring your Memgraph to production in mission-critical and high-availability workloads. +--- + +import { Callout } from 'nextra/components' +import { CommunityLinks } from '/components/social-card/CommunityLinks' + +# Memgraph in mission-critical workloads + + +Before diving into this guide, we recommend starting with the [Best +practices](/deployment/best-practices) + +page. It provides **foundational, use-case-agnostic advice** for deploying +Memgraph in production. + +This guide builds on that foundation, offering **additional recommendations +tailored to critical and high-availability workloads**. In cases where guidance +overlaps, consider the information here as **complementary or overriding**, +depending on the unique needs of your use case. + + +## Is this guide for you? + +This guide is for you if you're building **mission-critical systems** where +uptime, data consistency, and fault tolerance are essential. You’ll benefit +from this content if: + +- You require **high availability** and **automatic failover** for your + application. +- You need **strong consistency guarantees** even under heavy loads. +- You must **recover gracefully** from unexpected failures without data loss. +- You need to **support multi-tenant environments** securely across multiple + projects or customers. + + +If this matches your needs, this guide will help you configure and operate +Memgraph to meet the demands of **always-on production environments**. + +## Why choose Memgraph for mission-critical use cases? + +When stability, consistency, and resilience matter most, Memgraph is built to +deliver. Here's why Memgraph is a great fit for mission-critical workloads: + +- **In-memory storage engine with persistence** Memgraph keeps the working set + fully in memory for fast access, while ensuring + [durability](/fundamentals/data-durability) through **periodic snapshots** and + **write-ahead logging (WALs)** in transactional mode. + + Keeping the data in memory ensures lightning speed in times when you expect + everything to function seamlessly and without issues during peak times of your + critical service. + +- **High availability with automatic failover** Memgraph supports full [high + availability clustering](/clustering/high-availability), allowing you to + deploy **multiple instances** with automatic **leader election** and + **failover** when needed. + + Deploying Memgraph with high availability will ensure Memgraph is up and + running at all times, without compromising uptime of your services. + +- **Multi-version concurrency control (MVCC)** Built on **MVCC**, Memgraph + allows **non-blocking reads and writes**, ensuring that your system remains + **responsive** even under concurrent access. Writes are not blocking reads, + and vice versa. + +- **Snapshot isolation by default** Memgraph uses **snapshot isolation** instead + of **read-committed** isolation, preventing dirty reads and guaranteeing a + **consistent view** of the graph at all times. + +- **Replication for read scaling and redundancy** Memgraph supports + **asynchronous replication**, enabling you to **scale read workloads** + independently while ensuring **failover readiness**. For a more consistent + view of the data, it also supports **synchronous replication** which + prioritizes consistency over scalability. + +- **Fine-grained access control and security** Secure your system with + [**role-based access + control**](/database-management/authentication-and-authorization/role-based-access-control) + and [**label-based access + control**](/database-management/authentication-and-authorization/role-based-access-control#label-based-access-control) + to ensure only the right users see and manipulate data. + +## What is covered? + +The suggestions for mission-critical workloads **complement** several key +sections in the [general suggestions guide](/deployment/best-practices), with +additional best practices to ensure uptime and data protection: + +- [Choosing the right Memgraph flag set](#choose-the-right-memgraph-flag-set) + Memgraph offers flags to enhance recovery, snapshot management, and failover + capabilities. + +- [Choosing the right Memgraph storage + mode](#choose-the-right-memgraph-storage-mode) + Guidance on selecting the **safest** and **most consistent** storage + configurations. + +- [Enterprise features you might + require](#enterprise-features-you-might-require) + Overview of **replication**, **multi-tenancy**, and **automatic failover** + tools that are critical in production. + +- [Backup and recovery mechanisms](#backup-and-recovery-mechanisms) + Best practices to protect your data through snapshots, WALs, and external + backup strategies. + +- [Queries that best suit your workload](#queries-that-best-suit-your-workload) + Designing queries that maintain consistent, safe, and predictable behavior in + high-availability systems. + +## Choose the right Memgraph flag set + + +For mission-critical setups, you should configure Memgraph to optimize for **durability, fast recovery**, and **stability**. Some important flags include: + +- `--storage-snapshot-interval-sec=x` + Set how often snapshots are created. In mission-critical systems, you may want + **frequent snapshots** to minimize recovery time. + +- `--storage-wal-enabled=true` + Ensure **WALs (write-ahead logs)** are enabled to protect all transactions + between snapshots. + +- `--storage-parallel-schema-recovery=true` and + `--storage-recovery-thread-count=x` + Enable **parallel recovery** to speed up startup time after a crash by using + multiple cores. + +- `--query-execution-timeout-sec=x` + Set reasonable query timeouts to **avoid stuck queries** and prevent resource + exhaustion.` + +## Choose the right Memgraph storage mode + + +For mission-critical deployments: + +- Always use `IN_MEMORY_TRANSACTIONAL` mode. +- This mode provides **full ACID guarantees**, **WAL support**, and **snapshot + consistency**. + + +`IN_MEMORY_ANALYTICAL` is optimized for high-speed ingestion but does **not +provide transactional durability**. It is not recommended for mission-critical +workloads. + + +## Importing mechanisms + +Importing mechanisms are best described in the [guide for high-throughput +workloads](/deployment/workloads/memgraph-in-high-throughput-workloads). The +rule of thumb is to always setup the drivers to perform retries if you're doing +heavy amount of writes, in order to avoid read conflicts. The high throguhput +guide also outlines the need for idempotent queries, to ensure data consistency +if writes fail for any reason. + +## Enterprise features you might require + +For robust production environments, consider enabling: + +- [High availability clustering](/clustering/high-availability): Deploy multiple + Memgraph instances with automatic leader election and failover. + +- [Replication for resilience](/clustering/replication): Distribute replicas + geographically or across availability zones to minimize the risk of localized + outages. + +- [Role-based and label-based access + control](/database-management/authentication-and-authorization/role-based-access-control): + Protect sensitive graph data and ensure only authorized operations are + performed. + +- [Multi-tenancy](/database-management/multi-tenancy): Securely isolate data and + permissions between different teams, projects, or customers. + +## Backup and recovery mechanisms + +Data durability is critical in mission-critical environments. Memgraph supports: + +- [Snapshots](/fundamentals/data-durability#snapshots) + Automatically or manually triggered full-database snapshots. + +- [Write-ahead logging + (WALs)](/fundamentals/data-durability#write-ahead-logging) + Transaction logs that enable you to **replay changes** made after the last + snapshot. + +- **Manual backup and offloading** + Use external tools (like [`rclone`](https://rclone.org/)) to back up snapshots + and WALs to **cloud storage** or **remote servers** for additional redundancy. + + + +Memgraph currently does not automate backing up data to 3rd party locations, so +integrating a backup process into your system is highly recommended. + + + +Learn more about backup and restore [on our backup and restore documentation +page](/database-management/backup-and-restore). + + +## Queries that best suit your workload + +In mission-critical workloads: + +- Prefer **idempotent writes** (`MERGE`) to avoid inconsistent state during + retries. +- Optimize long-running queries and [profile](/querying/clauses/profile) them + regularly. + +- Avoid complex, unpredictable queries inside critical transactional paths. +- Use **schema constraints** and **indexes** wisely to enforce data integrity + without hurting performance. + +Example of safe, idempotent data ingestion: + +```cypher +MERGE (n:Customer {id: $id}) +SET n += $props; +``` + diff --git a/pages/fundamentals/data-durability.mdx b/pages/fundamentals/data-durability.mdx index 79679577b..10aa85aba 100644 --- a/pages/fundamentals/data-durability.mdx +++ b/pages/fundamentals/data-durability.mdx @@ -77,25 +77,41 @@ before being written to the DB, and in the end the log file contains all steps needed to reconstruct the DB’s most recent state. Memgraph has WAL enabled by default. To switch it on and off, use the boolean -`--storage-wal-enabled` flag. For other WAL-related flags check the [configuration -reference guide](/database-management/configuration#storage). +`--storage-wal-enabled` flag. For other WAL-related flags check the +[configuration reference guide](/database-management/configuration#storage). By default, WAL files are located at `/var/lib/memgraph/wal`. +

WAL file lifecycle

+ +**Older WAL files are deleted automatically after a snapshot is created** since +the snapshot contains the full database state up to that point. Only WAL files +containing changes after the latest snapshot are retained. + +To control WAL file cleanup indirectly, you can limit the number of snapshots +via `--storage-snapshot-retention-count`. + +**It is not possible to use WAL files exclusively** without snapshots. Memgraph +enforces periodic snapshots when WAL is enabled and will fail to start if WAL is +enabled with snapshot interval set to zero. + ### Snapshots Snapshots provide a faster way to restore the states of your database. Snapshots are created periodically based on the value defined with the -`--storage-snapshot-interval` configuration flags, as well as upon exit based -on the value of the `--storage-snapshot-on-exit` configuration flag. When a +`--storage-snapshot-interval` configuration flags, as well as upon exit based on +the value of the `--storage-snapshot-on-exit` configuration flag. When a snapshot creation is triggered, the entire data storage is written to the drive. Nodes and relationships are divided into groups called batches. - -If both flags `--storage-snapshot-interval` and `--storage-snapshot-interval-sec` are defined, the flag `--storage-snapshot-interval` will be used. + +If both flags `--storage-snapshot-interval` and +`--storage-snapshot-interval-sec` are defined, the flag +`--storage-snapshot-interval` will be used. -Snapshot creation can be made faster by using **multiple threads**. See [Parallelized execution](#parallelized-execution) for more information. +Snapshot creation can be made faster by using **multiple threads**. See +[Parallelized execution](#parallelized-execution) for more information. On startup, the database state is recovered from the most recent snapshot file. Memgraph can read the data and build the indexes on multiple threads, using @@ -115,25 +131,42 @@ WAL file and, if the snapshot is less recent, the state of the DB will be recovered using the WAL file. Memgraph has snapshot creation enabled by default. You can configure the exact -snapshot creation behavior by [defining the relevant flags](/database-management/configuration#storage). -Alternatively, you can make one directly by running the following query: +snapshot creation behavior by [defining the relevant +flags](/database-management/configuration#storage). Alternatively, you can make +one directly by running the following query: ```opencypher CREATE SNAPSHOT; ``` -If another snapshot is already being created or no committed writes to the database have been made since the last snapshot, this query will fail with an error. +If another snapshot is already being created or no committed writes to the +database have been made since the last snapshot, this query will fail with an +error. -By default, snapshot files are saved inside the `var/lib/memgraph/snapshots` directory. -The `CREATE SNAPSHOT` query will return the path of the newly created snapshot file. +By default, snapshot files are saved inside the `var/lib/memgraph/snapshots` +directory. The `CREATE SNAPSHOT` query will return the path of the newly created +snapshot file. To query which snapshots currently exist in the data directory, execute: ```opencypher SHOW SNAPSHOTS; ``` +

Snapshot and WAL recovery logic

+ +During recovery, Memgraph always attempts to use the fastest and most efficient +method to restore the database state: +- If the snapshot has a **more recent** timeline than the WAL, the database is +fully recovered from the latest snapshot. +- If the snapshot has a **less recent** timeline than the WAL, Memgraph first +recovers from the snapshot, and then replays WAL files containing changes made +after the snapshot was taken. This ensures recovery to the most recent state. +- Snapshot recovery is **typically faster** than recovery from WAL because +snapshots store the complete state of the database in a single file, while WAL +files store incremental changes and need to be replayed sequentially. + ### Periodic snapshots `IN_MEMORY_TRANSACTIONAL` mode supports periodic snapshot creation. The interval @@ -167,8 +200,9 @@ mode is active. The job will continue with the last defined interval when the storage mode is changed to `IN_MEMORY_TRANSACTIONAL` storage mode. -The periodic snapshot will be skipped if another snapshot is in progress or no new writes have been committed since the last snapshot. -If the periodic snapshot is skipped it will be logged on INFO level. +The periodic snapshot will be skipped if another snapshot is in progress or no +new writes have been committed since the last snapshot. If the periodic snapshot +is skipped it will be logged on INFO level. @@ -177,33 +211,55 @@ Snapshots and WAL files are presently not compatible between Memgraph versions. ### Parallelized execution -Snapshot creation in Memgraph can be optimized using multiple threads, which significantly reduces the time required to create snapshots for large datasets. +Snapshot creation in Memgraph can be optimized using multiple threads, which +significantly reduces the time required to create snapshots for large datasets. This behavior can be controlled using the following flags: -- `--storage-parallel-snapshot-creation`: This flag determines whether snapshot creation is performed in a multi-threaded fashion. By default, it is set to `false`. To enable parallelized execution, set this flag to `true`. -- `--storage-snapshot-thread-count`: This flag specifies the number of threads to be used for snapshot creation. By default, Memgraph uses the system's maximum thread count. You can override this value to fine-tune performance based on your system's resources. - -When parallelized execution is enabled, Memgraph divides the data into batches, where the batch size is defined via `--storage-items-per-batch`. The optimal batch size and thread count may vary depending on the dataset size and system configuration. - -#### When Parallelization Helps - -Parallel execution is especially beneficial when CPU-bound operations dominate the snapshot creation process, such as serialization or compression of in-memory structures. -As a general guideline, parallel snapshot creation provides the most significant performance improvement when disk I/O constitutes 25% or less of the total snapshot creation time. - -To take full advantage of parallelization, it’s also important to set the `--storage-items-per-batch` flag appropriately. This value determines how the dataset is split into work units for threads. -A good rule of thumb is: Total number of items (vertices + edges) ≈ 4 × number of threads × --storage-items-per-batch -This ensures that each thread has enough batches to work on without idling, helping maximize CPU utilization during snapshot creation. - -When using multi-threaded snapshot creation with the correct batch size, the disk will once again become the bottleneck. At that point, more threads will not necessarily yield better performance. - -##### Measuring Disk Write Speed on Linux -To determine how fast your disk can handle writes (which influences the I/O bottleneck), you can use the dd command: +- `--storage-parallel-snapshot-creation`: This flag determines whether snapshot + creation is performed in a multi-threaded fashion. By default, it is set to + `false`. To enable parallelized execution, set this flag to `true`. +- `--storage-snapshot-thread-count`: This flag specifies the number of threads + to be used for snapshot creation. By default, Memgraph uses the system's + maximum thread count. You can override this value to fine-tune performance + based on your system's resources. + +When parallelized execution is enabled, Memgraph divides the data into batches, +where the batch size is defined via `--storage-items-per-batch`. The optimal +batch size and thread count may vary depending on the dataset size and system +configuration. + +

When parallelization helps

+ +Parallel execution is especially beneficial when CPU-bound operations dominate +the snapshot creation process, such as serialization or compression of in-memory +structures. As a general guideline, parallel snapshot creation provides the most +significant performance improvement when disk I/O constitutes 25% or less of the +total snapshot creation time. + +To take full advantage of parallelization, it’s also important to set the +`--storage-items-per-batch` flag appropriately. This value determines how the +dataset is split into work units for threads. A good rule of thumb is: Total +number of items (vertices + edges) ≈ 4 × number of threads × +--storage-items-per-batch This ensures that each thread has enough batches to +work on without idling, helping maximize CPU utilization during snapshot +creation. + +When using multi-threaded snapshot creation with the correct batch size, the +disk will once again become the bottleneck. At that point, more threads will not +necessarily yield better performance. + +

Measuring disk write speed on Linux

+ +To determine how fast your disk can handle writes (which influences the I/O +bottleneck), you can use the dd command: ```bash dd if=/dev/zero of=testfile bs=1G count=1 oflag=direct ``` -This writes a 1 GB file directly to disk and reports the write speed. After the test, remove the file. +This writes a 1 GB file directly to disk and reports the write speed. After the +test, remove the file. -You can also monitor real-time disk utilization during snapshot creation using tools like `iostat`, `iotop`, or `dstat`. +You can also monitor real-time disk utilization during snapshot creation using +tools like `iostat`, `iotop`, or `dstat`. ## Storage modes diff --git a/pages/fundamentals/data-types.mdx b/pages/fundamentals/data-types.mdx index 4b24addb7..86f9d268f 100644 --- a/pages/fundamentals/data-types.mdx +++ b/pages/fundamentals/data-types.mdx @@ -622,7 +622,13 @@ CREATE (:Flight {AIR123: datetime("2021-04-21T14:15:00Z")}); Maps for constructing `ZonedDateTime` values may have the following fields: `year`, `month`, `day`, `hour`, `minute`, `second`, `millisecond`, -`microsecond` and `timezone`. +`microsecond` and `timezone`. +- If some numeric fields are omitted, they default to the lowest value for that field: + - `0` for `year`, `hour`, `minute`, `second`, `millisecond`, and `microsecond`. + - `1` for `month` and `day`. +- If the `timezone` is omitted, it defaults to UTC. +- If all numeric fields are omitted and only the `timezone` is specified, then a `datetime` +represents the **current time** in the that timezone. There are two options for the `timezone` field: * string: timezone name from the diff --git a/pages/getting-started/_meta.ts b/pages/getting-started/_meta.ts index 6f2d4b72a..0da9019e4 100644 --- a/pages/getting-started/_meta.ts +++ b/pages/getting-started/_meta.ts @@ -1,7 +1,8 @@ export default { "install-memgraph": "Install Memgraph", "cli": "CLI", - "first-steps-with-docker": "First steps with Docker" + "first-steps-with-docker": "First steps with Docker", + "build-memgraph-from-source": "Build Memgraph from source" } diff --git a/pages/getting-started/build-memgraph-from-source.mdx b/pages/getting-started/build-memgraph-from-source.mdx index 2adad95a6..38aab2488 100644 --- a/pages/getting-started/build-memgraph-from-source.mdx +++ b/pages/getting-started/build-memgraph-from-source.mdx @@ -1,5 +1,5 @@ --- -title: Building Memgraph from source +title: Build Memgraph from source description: This is a comprehensive guide for compiling Memgraph from source. It includes setting up the necessary toolchain, compiling the code, and running Memgraph. --- @@ -7,7 +7,7 @@ import { Callout } from 'nextra/components' import { Steps } from 'nextra/components' -# Building Memgraph from source +# Build Memgraph from source Follow this guide if you want to compile a Memgraph from a source. Here you will find all the necessary steps, including setting up the necessary toolchain, @@ -27,13 +27,9 @@ If you are using Mac M1 or above, please check our [MacOS Lima Compilation Guide](https://www.notion.so/MacOS-Lima-Compilation-Guide-eae1e9dcef5740579c5a41075b8f499b?pvs=21) first. -ARM build instructions are located at [Building Memgraph for ARM64 -CPU](https://www.notion.so/Building-Memgraph-for-ARM64-CPU-a73d243c3c7c4daa94cb574ca8ff9516?pvs=21) -document. - -## Obtaining the Source Code +## Obtain the Source Code After installing `git`, you are now ready to fetch your own copy of the Memgraph source code. Run the following command: @@ -44,16 +40,27 @@ git clone git@github.com:memgraph/memgraph.git The above will create a `memgraph` directory and put all source code there. -## Downloading the dependencies - -Before you can compile Memgraph, you first need to download its dependencies - In your terminal, position yourself in the obtained memgraph directory. ```bash cd memgraph ``` +

Choose build method

+ +There are three different methods for building Memgraph: + +1. Using the `build.sh` script (Recommended) +2. Manually with `conan` and `cmake` (Advanced) +3. Docker (ideal for unsupported systems) + +Before using methods 1 or 2, you must **download dependencies and install the +toolchain**. + +## Download dependencies (required for methods 1 & 2) + +Before you can compile Memgraph, you first need to download its dependencies. + Building Memgraph depends on some system-wide packages. The installation scripts can be found under `environment/os/`. The directory contains a dependencies management script for each supported operating system. @@ -63,17 +70,18 @@ sudo ./environment/os/install_deps.sh install TOOLCHAIN_RUN_DEPS sudo ./environment/os/install_deps.sh install MEMGRAPH_BUILD_DEPS ``` -The first command installs all the packages necessary for the Memgraph toolchain -to work correctly. The second command installs the system-wide packages that are -not necessary for the toolchain but are required by Memgraph. +- The first command installs all the packages necessary for the Memgraph +toolchain to work correctly. +- The second command installs the system-wide packages that are not necessary +for the toolchain but are required by Memgraph. - Based on your OS, version and architecture, execute appropriate scripts (e.g., on **Debian 11**, NOTE: the following commands/scripts are located under [memgraph repository](https://github.com/memgraph/memgraph/tree/master/environment/os): + Based on your OS, version and architecture, execute appropriate scripts (e.g., on **Debian 12**, NOTE: the following commands/scripts are located under [memgraph repository](https://github.com/memgraph/memgraph/tree/master/environment/os): ```bash - sudo ./environment/os/debian-11.sh install TOOLCHAIN_RUN_DEPS - sudo ./environment/os/debian-11.sh install MEMGRAPH_BUILD_DEPS + sudo ./environment/os/debian-12.sh install TOOLCHAIN_RUN_DEPS + sudo ./environment/os/debian-12.sh install MEMGRAPH_BUILD_DEPS ``` For ARM look for `-arm` in the script name (e.g., on Ubuntu 24.04 with Apple M processor): @@ -86,7 +94,7 @@ not necessary for the toolchain but are required by Memgraph. Once everything is installed, you can proceed to the compilation. -## Compiling +## Toolchain installation (required for methods 1 & 2) Memgraph is compiled using our own custom toolchain that can be obtained from the toolchain repository. All our tools used in the development of Memgraph are @@ -106,20 +114,20 @@ You should read the [Toolchain](https://www.notion.so/Toolchain-37c37c84382149a58d09b2ccfcb410d7?pvs=21) to install the appropriate toolchain for your distribution. -### Toolchain installation procedure - Download the toolchain for your operating system from one of the following links: -- [CentOS 9](https://s3-eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v6/toolchain-v6-binaries-centos-9-x86_64.tar.gz) -- [CentOS 10](https://s3-eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v6/toolchain-v6-binaries-centos-10-x86_64.tar.gz) -- [Debian 11 (x86_64)](https://s3-eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v6/toolchain-v6-binaries-debian-11-amd64.tar.gz) -- [Debian 11 (arm64)](https://s3-eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v6/toolchain-v6-binaries-debian-11-arm64.tar.gz) -- [Debian 12 (x86_64)](https://s3.eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v6/toolchain-v6-binaries-debian-12-amd64.tar.gz) -- [Debian 12 (arm64)](https://s3.eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v6/toolchain-v6-binaries-debian-12-arm64.tar.gz) -- [Fedora 41 (x86_64)](https://s3.eu-west-1.amazonaws.com/download.memgraph.com/memgraph/v3.1.1/fedora-41/memgraph-3.1.1_1-1.x86_64.rpm) -- [Ubuntu 22.04 (x86_64)](https://s3-eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v6/toolchain-v6-binaries-ubuntu-22.04-amd64.tar.gz) -- [Ubuntu 24.04 (x86_64)](https://s3-eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v6/toolchain-v6-binaries-ubuntu-24.04-amd64.tar.gz) -- [Ubuntu 24.04 (arm64)](https://s3-eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v6/toolchain-v6-binaries-ubuntu-24.04-arm64.tar.gz) +- [CentOS 9](https://s3-eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v7/toolchain-v7-binaries-centos-9-x86_64.tar.gz) +- [CentOS 10](https://s3-eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v7/toolchain-v7-binaries-centos-10-x86_64.tar.gz) +- [Debian 12 (x86_64)](https://s3-eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v7/toolchain-v7-binaries-debian-12-amd64.tar.gz) +- [Debian 12 (arm64)](https://s3-eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v7/toolchain-v7-binaries-debian-12-arm64.tar.gz) +- [Debian 13 (x86_64)](https://s3.eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v7/toolchain-v7-binaries-debian-13-amd64.tar.gz) +- [Debian 13 (arm64)](https://s3.eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v7/toolchain-v7-binaries-debian-13-arm64.tar.gz) +- [Fedora 42 (x86_64)](https://s3.eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v7/toolchain-v7-binaries-fedora-42-x86_64.tar.gz) +- [Fedora 42 (arm64)](https://s3.eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v7/toolchain-v7-binaries-fedora-42-aarch64.tar.gz) +- [Rocky Linux 10 (x86_64)](https://s3.eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v7/toolchain-v7-binaries-rocky-10-x86_64.tar.gz) +- [Ubuntu 22.04 (x86_64)](https://s3-eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v7/toolchain-v7-binaries-ubuntu-22.04-amd64.tar.gz) +- [Ubuntu 24.04 (x86_64)](https://s3-eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v7/toolchain-v7-binaries-ubuntu-24.04-amd64.tar.gz) +- [Ubuntu 24.04 (arm64)](https://s3-eu-west-1.amazonaws.com/deps.memgraph.io/toolchain-v7/toolchain-v7-binaries-ubuntu-24.04-arm64.tar.gz) Extract the toolchain with the following command: @@ -130,101 +138,170 @@ sudo tar xzvfm {{toolchain-archive}}.tar.gz -C /opt After you have installed the toolchain, you should read the instructions for the -toolchain in the toolchain install directory (`/opt/toolchain-v6/README.md`) +toolchain in the toolchain install directory (`/opt/toolchain-v7/README.md`) and install dependencies that are necessary to run the toolchain. If you have not already installed toolchain dependencies, please check and -install required toolchain runtime dependencies by executing +install required toolchain runtime dependencies as in the section above. + + + +If you put the toolchain on some other path, it’s possible to say to the `cmake` +the root is there, that is done by [setting `MG_TOOLCHAIN_ROOT` environment +variable](https://www.notion.so/If-you-put-toolchain-on-some-other-path-it-s-possible-to-say-to-the-cmake-there-the-root-is-that-s-e45311092e9a454eb73c720bf9ef04c1?pvs=21). + +That’s also useful where you have different versions of libraries under system +compare to what the Memgraph build process needs. + + + +## Use `build.sh` script + +This method is the easiest way to build Memgraph directly on a compatible host +system. + +Calling the script with no arguments will build everything, including tests, for +the `Release` build type: ```bash -sudo ./environment/os/install_deps.sh check TOOLCHAIN_RUN_DEPS -sudo ./environment/os/install_deps.sh install TOOLCHAIN_RUN_DEPS +./build.sh ``` - +Optionally you can specify target and build types, e.g. - Based on your OS, version and architecture, execute appropriate scripts (e.g., on Debian 11, NOTE: the following commands/scripts are located under [memgraph repository](https://github.com/memgraph/memgraph)): +```bash +./build.sh --target memgraph --build-type Debug +``` - ```bash - sudo ./environment/os/debian-11.sh check TOOLCHAIN_RUN_DEPS - sudo ./environment/os/debian-11.sh install TOOLCHAIN_RUN_DEPS - ``` - - For ARM look for `-arm` in script name (e.g. on Ubuntu 24.04 with Apple M processor): - - ```bash - sudo ./environment/os/ubuntu-24.04-arm.sh check TOOLCHAIN_RUN_DEPS - sudo ./environment/os/ubuntu-24.04-arm.sh install TOOLCHAIN_RUN_DEPS - ``` - +where the build type can be `Release` (default), `Debug` or `RelWithDebInfo`. + + +Other cmake options can be passed as well, e.g. to disable testing: + +```bash +./build.sh --target memgraph --build-type Release -DMG_ENABLE_TESTING=OFF +``` + +The resulting binary will be in the `build/` directory. + +## Use `conan` and `cmake` -When you want to compile Memgraph, you should activate the toolchain using the -prepared toolchain activation script that is also described in the toolchain -`README`. +This approach offers greater flexibility and granular control over the build process. +While it performs the same operations as the `build.sh` script, it gives you direct access +to configure individual build parameters and dependencies. -You must activate the toolchain every time you want to compile Memgraph: +To build Memgraph using this method, follow these steps: + + +

Create a Python virtual environment and install `conan`

```bash -source /opt/toolchain-v6/activate +python3 -m venv env +source env/bin/activate +pip install conan +conan profile detect ``` -In case you need to deactivate the toolchain, you can run: +

Run the init script to fetch other libs required for the build

```bash -deactivate +./init ``` - +

Install conan dependencies

-If you put the toolchain on some other path, it’s possible to say to the `cmake` -the root is there, that is done by [setting `MG_TOOLCHAIN_ROOT` environment -variable](https://www.notion.so/If-you-put-toolchain-on-some-other-path-it-s-possible-to-say-to-the-cmake-there-the-root-is-that-s-e45311092e9a454eb73c720bf9ef04c1?pvs=21). +```bash +export MG_TOOLCHAIN_ROOT=/opt/toolchain-v7 +conan install . --build=missing -pr ./memgraph_template_profile -s build_type=Release +source build/generators/conanbuild.sh +``` -That’s also useful where you have different versions of libraries under system -compare to what the Memgraph build process needs. +

Configure the project with cmake

- +Note that the name of the preset depends on the build type set in the previous +step. + +```bash +cmake --preset conan-release +``` -## Installing Memgraph dependencies +

Build the project

-In addition to the system-wide dependencies, Memgraph requires certain libraries -to be built locally. The proper setup of these libraries should be checked by -running the `init` script: +The following command will build everything, including tests. ```bash -./init +cmake --build --preset conan-release -j$(nproc) ``` - +

Or for a specific target (e.g. Memgraph binary)

-Make sure to activate the toolchain before the `./init` command. +```bash +cmake --build --preset conan-release --target memgraph -j$(nproc) +``` + - -With all of the dependencies installed and the build environment set-up, you -need to configure the build system. To do that, execute the following: +## Use Docker + +Start by setting the environment variables for the desired OS, architecture, and build type: ```bash -mkdir -p build -cd build -cmake .. +export OS="ubuntu-24.04" +export ARCH="amd" # or arm +export BUILD_TYPE="Release" +export TOOLCHAIN="v7" ``` -If only Memgraph binary is required you can run build using: +Next, pull the appropriate Docker image for the build, e.g.: -```jsx -make -j$(nproc) memgraph +```bash +docker pull memgraph/mgbuild:v7_ubuntu-24.04 ``` -If you need to compile the whole project (e.g., unit tests) run: +Available image tags can be found [here](https://hub.docker.com/r/memgraph/mgbuild/tags). + +Then spin up the container: ```bash -make -j$(nproc) +./release/package/mgbuild.sh \ + --toolchain $TOOLCHAIN \ + --os $OS \ + --arch $ARCH \ + --build-type $BUILD_TYPE \ + run ``` -## Running Memgraph +Then build Memgraph: +```bash +./release/package/mgbuild.sh \ + --toolchain $TOOLCHAIN \ + --os $OS \ + --arch $ARCH \ + --build-type $BUILD_TYPE \ + build-memgraph +``` + +Run Memgraph inside the container (the name of the container will look something like `mgbuild_v7_ubuntu-24.04`): +```bash +# find the name of the container +docker ps + +# run Memgraph +docker exec -i mgbuild_v7_ubuntu-24.04 bash -c "cd /home/mg/memgraph && ./build/memgraph" +``` + +Stop the container: +```bash +./release/package/mgbuild.sh \ + --toolchain $TOOLCHAIN \ + --os $OS \ + --arch $ARCH \ + stop --remove +``` + +## Run Memgraph After the compilation, verify that Memgraph works: @@ -232,8 +309,20 @@ After the compilation, verify that Memgraph works: ./memgraph --version ``` -The unit tests can be run using +The unit tests can be run using: ```bash ctest -R unit -j$(nproc) ``` + +Or in Docker: + +```bash +./release/package/mgbuild.sh \ + --toolchain $TOOLCHAIN \ + --os $OS \ + --arch $ARCH \ + --enterprise-license $MEMGRAPH_ENTERPRISE_LICENSE \ + --organization-name $MEMGRAPH_ORGANIZATION_NAME \ + test-memgraph unit +``` diff --git a/pages/getting-started/install-memgraph.mdx b/pages/getting-started/install-memgraph.mdx index 2f468fba1..70cf61d1f 100644 --- a/pages/getting-started/install-memgraph.mdx +++ b/pages/getting-started/install-memgraph.mdx @@ -83,7 +83,7 @@ installation options and pick the preferred one. href="/getting-started/install-memgraph/wsl" /> diff --git a/pages/getting-started/install-memgraph/debian.mdx b/pages/getting-started/install-memgraph/debian.mdx index 33faf1e46..f1b392cef 100644 --- a/pages/getting-started/install-memgraph/debian.mdx +++ b/pages/getting-started/install-memgraph/debian.mdx @@ -9,7 +9,7 @@ import CodeSnippet from '/components/code-snippet/CodeSnippet' # Install Memgraph on Debian -Install and run Memgraph on Debian 11 or Debian 12. +Install and run Memgraph on Debian 12 or Debian 13. Newer versions of Memgraph might not be backward diff --git a/pages/getting-started/install-memgraph/direct-download-links.mdx b/pages/getting-started/install-memgraph/direct-download-links.mdx index b86f7a11d..65267b4bb 100644 --- a/pages/getting-started/install-memgraph/direct-download-links.mdx +++ b/pages/getting-started/install-memgraph/direct-download-links.mdx @@ -11,32 +11,32 @@ Download Hub](https://memgraph.com/download/). If you need direct links for the latest version of Memgraph database, take a look at the list below. ## Docker -- [https://download.memgraph.com/memgraph/v3.5.0/docker/memgraph-3.5.0-docker.tar.gz](https://download.memgraph.com/memgraph/v3.5.0/docker/memgraph-3.5.0-docker.tar.gz) -- [https://download.memgraph.com/memgraph/v3.5.0/docker-aarch64/memgraph-3.5.0-docker.tar.gz](https://download.memgraph.com/memgraph/v3.5.0/docker-aarch64/memgraph-3.5.0-docker.tar.gz) -- [https://download.memgraph.com/memgraph/v3.5.0/docker-relwithdebinfo/memgraph-3.5.0-relwithdebinfo-docker.tar.gz](https://download.memgraph.com/memgraph/v3.5.0/docker-relwithdebinfo/memgraph-3.5.0-relwithdebinfo-docker.tar.gz) -- [https://download.memgraph.com/memgraph/v3.5.0/docker-aarch64-relwithdebinfo/memgraph-3.5.0-relwithdebinfo-docker.tar.gz](https://download.memgraph.com/memgraph/v3.5.0/docker-aarch64-relwithdebinfo/memgraph-3.5.0-relwithdebinfo-docker.tar.gz) +- [https://download.memgraph.com/memgraph/v3.6.0/docker/memgraph-3.6.0-docker.tar.gz](https://download.memgraph.com/memgraph/v3.6.0/docker/memgraph-3.6.0-docker.tar.gz) +- [https://download.memgraph.com/memgraph/v3.6.0/docker-aarch64/memgraph-3.6.0-docker.tar.gz](https://download.memgraph.com/memgraph/v3.6.0/docker-aarch64/memgraph-3.6.0-docker.tar.gz) +- [https://download.memgraph.com/memgraph/v3.6.0/docker-relwithdebinfo/memgraph-3.6.0-relwithdebinfo-docker.tar.gz](https://download.memgraph.com/memgraph/v3.6.0/docker-relwithdebinfo/memgraph-3.6.0-relwithdebinfo-docker.tar.gz) +- [https://download.memgraph.com/memgraph/v3.6.0/docker-aarch64-relwithdebinfo/memgraph-3.6.0-relwithdebinfo-docker.tar.gz](https://download.memgraph.com/memgraph/v3.6.0/docker-aarch64-relwithdebinfo/memgraph-3.6.0-relwithdebinfo-docker.tar.gz) ## Linux Memgraph can be run on the Linux distributions listed below. ### CentOS -- [https://download.memgraph.com/memgraph/v3.5.0/centos-9/memgraph-3.5.0_1-1.x86_64.rpm](https://download.memgraph.com/memgraph/v3.5.0/centos-9/memgraph-3.5.0_1-1.x86_64.rpm) -- [https://download.memgraph.com/memgraph/v3.5.0/centos-10/memgraph-3.5.0_1-1.x86_64.rpm](https://download.memgraph.com/memgraph/v3.5.0/centos-10/memgraph-3.5.0_1-1.x86_64.rpm) +- [https://download.memgraph.com/memgraph/v3.6.0/centos-9/memgraph-3.6.0_1-1.x86_64.rpm](https://download.memgraph.com/memgraph/v3.6.0/centos-9/memgraph-3.6.0_1-1.x86_64.rpm) +- [https://download.memgraph.com/memgraph/v3.6.0/centos-10/memgraph-3.6.0_1-1.x86_64.rpm](https://download.memgraph.com/memgraph/v3.6.0/centos-10/memgraph-3.6.0_1-1.x86_64.rpm) ### Debian -- [https://download.memgraph.com/memgraph/v3.5.0/debian-11/memgraph_3.5.0-1_amd64.deb](https://download.memgraph.com/memgraph/v3.5.0/debian-11/memgraph_3.5.0-1_amd64.deb) -- [https://download.memgraph.com/memgraph/v3.5.0/debian-12/memgraph_3.5.0-1_amd64.deb](https://download.memgraph.com/memgraph/v3.5.0/debian-12/memgraph_3.5.0-1_amd64.deb) +- [https://download.memgraph.com/memgraph/v3.6.0/debian-11/memgraph_3.6.0-1_amd64.deb](https://download.memgraph.com/memgraph/v3.6.0/debian-11/memgraph_3.6.0-1_amd64.deb) +- [https://download.memgraph.com/memgraph/v3.6.0/debian-12/memgraph_3.6.0-1_amd64.deb](https://download.memgraph.com/memgraph/v3.6.0/debian-12/memgraph_3.6.0-1_amd64.deb) ### Fedora -- [https://download.memgraph.com/memgraph/v3.5.0/fedora-41/memgraph-3.5.0_1-1.x86_64.rpm](https://download.memgraph.com/memgraph/v3.5.0/fedora-41/memgraph-3.5.0_1-1.x86_64.rpm) +- [https://download.memgraph.com/memgraph/v3.6.0/fedora-41/memgraph-3.6.0_1-1.x86_64.rpm](https://download.memgraph.com/memgraph/v3.6.0/fedora-41/memgraph-3.6.0_1-1.x86_64.rpm) ### Red Hat -- [https://download.memgraph.com/memgraph/v3.5.0/centos-9/memgraph-3.5.0_1-1.x86_64.rpm](https://download.memgraph.com/memgraph/v3.5.0/centos-9/memgraph-3.5.0_1-1.x86_64.rpm) +- [https://download.memgraph.com/memgraph/v3.6.0/centos-9/memgraph-3.6.0_1-1.x86_64.rpm](https://download.memgraph.com/memgraph/v3.6.0/centos-9/memgraph-3.6.0_1-1.x86_64.rpm) ### Ubuntu -- [https://download.memgraph.com/memgraph/v3.5.0/ubuntu-22.04/memgraph_3.5.0-1_amd64.deb](https://download.memgraph.com/memgraph/v3.5.0/ubuntu-22.04/memgraph_3.5.0-1_amd64.deb) -- [https://download.memgraph.com/memgraph/v3.5.0/ubuntu-24.04/memgraph_3.5.0-1_amd64.deb](https://download.memgraph.com/memgraph/v3.5.0/ubuntu-24.04/memgraph_3.5.0-1_amd64.deb) -- [https://download.memgraph.com/memgraph/v3.5.0/ubuntu-24.04-relwithdebinfo/memgraph_3.5.0-1_amd64.deb](https://download.memgraph.com/memgraph/v3.5.0/ubuntu-24.04-relwithdebinfo/memgraph_3.5.0-1_amd64.deb) -- [https://download.memgraph.com/memgraph/v3.5.0/ubuntu-24.04-aarch64/memgraph_3.5.0-1_arm64.deb](https://download.memgraph.com/memgraph/v3.5.0/ubuntu-24.04-aarch64/memgraph_3.5.0-1_arm64.deb) -- [https://download.memgraph.com/memgraph/v3.5.0/ubuntu-24.04-aarch64-relwithdebinfo/memgraph_3.5.0-1_arm64.deb](https://download.memgraph.com/memgraph/v3.5.0/ubuntu-24.04-aarch64-relwithdebinfo/memgraph_3.5.0-1_arm64.deb) +- [https://download.memgraph.com/memgraph/v3.6.0/ubuntu-22.04/memgraph_3.6.0-1_amd64.deb](https://download.memgraph.com/memgraph/v3.6.0/ubuntu-22.04/memgraph_3.6.0-1_amd64.deb) +- [https://download.memgraph.com/memgraph/v3.6.0/ubuntu-24.04/memgraph_3.6.0-1_amd64.deb](https://download.memgraph.com/memgraph/v3.6.0/ubuntu-24.04/memgraph_3.6.0-1_amd64.deb) +- [https://download.memgraph.com/memgraph/v3.6.0/ubuntu-24.04-relwithdebinfo/memgraph_3.6.0-1_amd64.deb](https://download.memgraph.com/memgraph/v3.6.0/ubuntu-24.04-relwithdebinfo/memgraph_3.6.0-1_amd64.deb) +- [https://download.memgraph.com/memgraph/v3.6.0/ubuntu-24.04-aarch64/memgraph_3.6.0-1_arm64.deb](https://download.memgraph.com/memgraph/v3.6.0/ubuntu-24.04-aarch64/memgraph_3.6.0-1_arm64.deb) +- [https://download.memgraph.com/memgraph/v3.6.0/ubuntu-24.04-aarch64-relwithdebinfo/memgraph_3.6.0-1_arm64.deb](https://download.memgraph.com/memgraph/v3.6.0/ubuntu-24.04-aarch64-relwithdebinfo/memgraph_3.6.0-1_arm64.deb) diff --git a/pages/getting-started/install-memgraph/fedora.mdx b/pages/getting-started/install-memgraph/fedora.mdx index 230cb65f7..89c828ed5 100644 --- a/pages/getting-started/install-memgraph/fedora.mdx +++ b/pages/getting-started/install-memgraph/fedora.mdx @@ -10,7 +10,7 @@ import CodeSnippet from '/components/code-snippet/CodeSnippet' # Install Memgraph on Fedora from RPM package Install and run Memgraph from a RPM package on: - - **Fedora 41** + - **Fedora 42** Newer versions of Memgraph might not be backward @@ -32,9 +32,9 @@ You can also use [direct download links](/getting-started/install-memgraph/direct-download-links) to get the latest Memgraph packages. -For example, for Fedora 39: +For example, for Fedora 42: - + @@ -50,7 +50,7 @@ After downloading the Memgraph RPM package, you can install it by issuing the following command: ``` console -sudo dnf install -y ./memgraph-3.1.1_1-1.x86_64.rpm +sudo dnf install -y ./memgraph-3.7.0_1-1.x86_64.rpm ``` If you run into any troubles while installing Memgraph, contact us on diff --git a/pages/getting-started/install-memgraph/rocky.mdx b/pages/getting-started/install-memgraph/rocky.mdx index 045ad9073..a0ff55afd 100644 --- a/pages/getting-started/install-memgraph/rocky.mdx +++ b/pages/getting-started/install-memgraph/rocky.mdx @@ -9,15 +9,9 @@ import CodeSnippet from '/components/code-snippet/CodeSnippet' # Install Memgraph on Rocky from RPM package - -The last released Memgraph RPM package for Rocky was for version 3.0.0. If you -require a package for a newer version, please [open an -issue](https://github.com/memgraph/memgraph/issues) on the Memgraph GitHub -repository. - Install and run Memgraph from a RPM package on: - - **Rocky 9.3** + - **Rocky 10** Newer versions of Memgraph might not be backward @@ -41,7 +35,7 @@ latest Memgraph packages. For example: - + @@ -57,7 +51,7 @@ After downloading the Memgraph RPM package, you can install it by issuing the following command: ``` -sudo dnf install -y ./memgraph-3.0.0_1-1.x86_64.rpm +sudo dnf install -y ./memgraph-3.7.0_1-1.x86_64.rpm ``` If you run into any troubles while installing Memgraph, contact us on diff --git a/pages/memgraph-lab/features/graphchat.mdx b/pages/memgraph-lab/features/graphchat.mdx index 012c4e220..392d67db3 100644 --- a/pages/memgraph-lab/features/graphchat.mdx +++ b/pages/memgraph-lab/features/graphchat.mdx @@ -29,13 +29,14 @@ endpoint, headers, retry logic, and context preferences. 2. [**Start chatting**](#chat-interface): Once connected, open the chat interface. You can create multiple threads to organize conversations by topic, -question type, or model comparison. Each question–answer pair is stored as an +question type, or model comparison. Each question - answer pair is stored as an exchange, which can be reused as context in future prompts. -3. **Let GraphChat handle the rest**: GraphChat automatically selects the most -appropriate tool—whether generating a Cypher query, running an algorithm, or -inspecting metadata. You can review, adjust, or expand any answer to inspect the -LLM's reasoning process and control the prompt context. +3. **Let GraphChat handle the rest**: GraphChat +automatically selects the most appropriate tool - whether it’s a built-in tool, +a custom tool, or even a remote MCP server - when generating a Cypher query, +running an algorithm, or inspecting metadata. You can review, adjust, or expand +any answer to inspect the LLM's reasoning process and control the prompt context. From Memgraph 2.16, GraphChat doesn't require MAGE to be installed. For schema @@ -166,7 +167,11 @@ Additional settings allow for more control: can take when using tools to answer a question. More steps enable deeper problem-solving but may increase latency and usage costs. - **LLM permissions** - Limit the changes GraphChat can make to your database. -- **Additional context** – Include extra contextual information as needed. +- **System instructions** – Define the assistant's role, tone, and behavior. These + instructions are always included at the start of the prompt. +- **System additional context** – Select predefined modules (graph schema, Cypher + query specifics, various constraints) to enrich the assistant's context. These + are appended to the system instructions. You can also create multiple configurations for the same model to suit different use cases. @@ -194,55 +199,158 @@ To adjust this: exchanges directly from the conversation view for even more customization. -To generate responses, GraphChat leverages [prompt context](#prompt-context) and -[built-in tools](#built-in-tools). [Exploring exchanges](#explore-exchanges) +To generate responses, GraphChat leverages: +- [Prompt context](#prompt-context) - GraphChat constructs a detailed prompt that defines the assistant’s role, tone, and permissions, optionally including schema and Cypher-specific guidance to ensure accurate and context-aware responses. +- [Tools](#tools) - A collection of built-in and custom Cypher-backed tools that let the LLM query data, analyze graphs, and interact directly with the Memgraph database. +- [MCP servers](#mcp-servers) - External tool integrations that expand GraphChat’s capabilities by connecting to third-party or custom MCP servers through configurable connections. +- [Exploring exchanges](#explore-exchanges) - Lets you inspect the LLM’s reasoning process, view which tools were used, and examine the full context and schema involved in generating each response. gives you deeper insight into the LLM's reasoning process. ### Prompt context -When you pose a question, GraphChat builds a **prompt context** for the LLM that -includes: +When you ask a question, GraphChat constructs a **prompt context** for the +LLM that includes: + +* **Introduction** - Define the assistant’s role, tone, and behavior. + These instructions are always included at the start of the prompt. + You can edit the default settings by adding new rules or completely + redefining the role, tone, and behavior of the assistant. +* **Graph schema (*Optional*)** - If selected, Lab ensures that each LLM + interaction has access to the graph schema. Without it, the LLM will + attempt to infer the schema on its own. +* **Query permissions (*Optional*)** - If enabled, Lab updates the prompt + context with query constraints, specifying whether the assistant can + read, update, insert, and/or delete data in Memgraph. +* **Cypher-specific notes (*Optional*)** - Provides rules and guidance + where Memgraph's Cypher syntax differs from other Cypher-based + databases. -* Introduction -* Schema -* Constraints -* Cypher-specific notes -* Additional (user-provided) context + +**Note**: Large graph schemas can consume significant tokens in the LLM's +context window. In such cases, consider disabling automatic inclusion of +the graph schema to optimize cost and performance. + + +![graphchat-model-prompt-edit](/pages/data-visualization/features/graphchat/graphchat-model-prompt.png) + +### Tools -### Built-in tools +GraphChat includes a set of **built-in tools** and supports +creating **custom Cypher-backed tools**. + +{

Built-in tools

} + +Built-in tools cover a variety of tasks such as querying data, +retrieving database information, running graph algorithms, +checking indexes, managing triggers, and more: -GraphChat gives models access to built-in tools that allow them to query your -data, inspect the database, and run algorithms: * `run-cypher-query`: Generate and execute a Cypher query. -* `run-page-rank`: Identify the most connected and impactful node using PageRank. -* `run-betweenness-centrality`: Determine which nodes serve as critical bridges in the graph. -* `show-config`: List all Memgraph database configuration parameters. -* `show-schema-info`: Display the full database schema (requires `--schema-info-enabled` flag on startup). -* `show-storage-info`: View memory usage, available memory, disk usage, and counts of nodes and relationships. +* `run-page-rank`: Identify the most connected and impactful + node using PageRank. +* `run-betweenness-centrality`: Determine which nodes serve + as critical bridges in the graph. +* `show-config`: List all Memgraph database configuration + parameters. +* `show-schema-info`: Display the full database schema + (requires `--schema-info-enabled` flag on startup). +* `show-storage-info`: View memory usage, available memory, + disk usage, and counts of nodes and relationships. * `show-indexes`: List all database indexes. * `show-constraints`: List all defined constraints. * `show-triggers`: List all active triggers. -{

Tool usage before Lab 3.3

} +![graphchat-toolkit-builtin](/pages/data-visualization/features/graphchat/toolkit-builtin.png) + + +**Tool usage before Lab 3.3** In earlier versions, GraphChat only used the `run-cypher-query` tool. This tool: + * Generates and runs Cypher queries from LLM prompts -* **Automatically retries invalid queries** up to the retry limit defined in the model configuration +* **Automatically retries invalid queries** up to the retry limit defined in + the model configuration + +If you want to replicate this behavior, disable all other tools in the +configuration. + + +{

Cypher-backed tool

} + +From Lab 3.3 onward, you can also define your own custom +tools by providing: + +* A tool name +* A description +* A parameterized Cypher query to execute on call + +![graphchat-toolkit-custom](/pages/data-visualization/features/graphchat/toolkit-custom.png) + +Make sure each custom tool has a unique name and clear description +so the LLM can accurately select the appropriate tool when responding. -If you want to replicate this behavior, disable all other tools in the configuration. +### MCP servers -{

Enhanced tool support from Lab 3.3 onward

} +Starting with Lab 3.6, you can integrate tools from MCP servers, +where Lab acts as an MCP client. This greatly expands the +capabilities of the assistant in GraphChat, allowing it to +leverage external tools beyond the built-in and custom ones. -Starting with Lab 3.3, GraphChat can use all built-in tools automatically. The -LLM decides which tool to use based on the context of the question. +![mcp-servers-settings](/pages/data-visualization/features/graphchat/mcp-servers-settings.png) -You can also define your own **custom tools** by providing: -* A **tool name** -* A **description** -* A **parameterized Cypher query** +{

Setting up the connection

} -Ensure each custom tool has a distinct name and description so the LLM can -choose the right one. +In Settings/LLM tab, you can create and manage MCP connections. +Lab currently supports a streamable HTTP transport layer. To +set up a connection: + +* Enter the **URL** where your MCP server is listening. +* (Optional) Add an **access token** - it will be sent as an + Authorization header. +* (Optional) Add any **custom headers** required by your MCP server. + +Upon a successful connection, Lab retrieves a list of tools provided +by the MCP server. You can then select which of these tools you +want to enable in GraphChat. + +GraphChat automatically resyncs tools and MCP connections each +time you open a new GraphChat view. If there's an issue with a +connection, the affected tools will be unavailable, and you'll +see the error response that explains why the connection +failed - helping you troubleshoot and resolve the issue. + +{

Managing MCP tools in GraphChat

} + +Once an MCP connection is set up in Lab, you can manage its +tools directly within GraphChat. When you open the tools list +from the input box in GraphChat, you'll see: + +* All your active MCP servers +* The tools each server provides + +![toolkit-mcp](/pages/data-visualization/features/graphchat/toolkit-mcp.png) + +You can choose which tools to enable for the current GraphChat +conversation. Additionally, you can quickly enable or disable +all tools from a specific MCP server with a single action - making +it easy to tailor the toolset to your workflow. + +{

Examples

} + +Tavily Integration: + +* Enter `https://mcp.tavily.com/mcp/` in the URL field. +* Register on Tavily to obtain an access token and add it + in the Access Token field. + +![mcp-create-tavily](/pages/data-visualization/features/graphchat/mcp-create-tavily.png) + +Memgraph MCP Integration: + +* Pull the [ai-toolkit/memgraph](https://github.com/memgraph/ai-toolkit/tree/main/integrations/mcp-memgraph) repository. +* Build the provided Dockerfile to start the MCP server. +* Enter `https://localhost:8000/mcp/` in the URL field. + +![mcp-create-memgraph](/pages/data-visualization/features/graphchat/mcp-create-memgraph.png) ### Explore exchanges @@ -253,10 +361,10 @@ raw response from the Assistant. You can also explore: * **Number of previous exchanges**, **tokens**, and **tools used** -* **Schema used** – Click to visualize the included schema +* **Schema used** – Click to visualize the included schema if schema was + generated for the prompt by the Lab * **Context used** – Click to view the full prompt context sent to the LLM - ## Resources - [Talking to Your Graph Database with LLMs Using GraphChat](https://memgraph.com/blog/talking-to-graph-database-llms-graphchat-webinar-recap) diff --git a/pages/memgraph-lab/features/single-sign-on.mdx b/pages/memgraph-lab/features/single-sign-on.mdx index 17cfb6ec6..cbffdfaaf 100644 --- a/pages/memgraph-lab/features/single-sign-on.mdx +++ b/pages/memgraph-lab/features/single-sign-on.mdx @@ -319,4 +319,19 @@ AUTH_SAML_CUSTOM_ISSUER=http:///realms/myrealm AUTH_SAML_CUSTOM_CALLBACK_URL=http:///auth/providers/saml-custom/callback ``` +{

Registering custom CA certificates

} + +If your custom Identity Provider uses self-signed certificates, Lab may +block access to unverified resources with the error **"unable to get local issuer certificate"**. +To resolve this, Lab needs to recognize those certificates. Make sure +to mount them and register them in the Docker container using the following +environment variable: + +``` +docker run \ + ... + -e NODE_EXTRA_CA_CERTS=path/to/ca-certificates-mounted-in-docker-container.crt + memgraph/lab +``` + \ No newline at end of file diff --git a/pages/memgraph-lab/querying.mdx b/pages/memgraph-lab/querying.mdx index 73f7183de..63f003f6d 100644 --- a/pages/memgraph-lab/querying.mdx +++ b/pages/memgraph-lab/querying.mdx @@ -238,6 +238,12 @@ also expand and collapse nodes with a double-click. ![](/pages/data-visualization/lab-user-manual/graph-results.png) +Moreover, you can use the search bar above the graph to quickly find nodes by name. +As you type, matching nodes appear in the results list, and hovering over or selecting one +will highlight it directly on the graph. + +![](/pages/data-visualization/lab-user-manual/graph-search-bar.png) + {

Graph customization

} To customize the appearance of the graph you can update the GSS in the [Graph diff --git a/pages/release-notes.mdx b/pages/release-notes.mdx index ad4f6dd5c..8381438f1 100644 --- a/pages/release-notes.mdx +++ b/pages/release-notes.mdx @@ -42,6 +42,47 @@ troubleshoot in production. ## 🚀 Latest release +### Memgraph v3.6.1 - October 16th, 2025 + +{

⚠️ Breaking changes

} + +- Changed the behaviour of calls like `datetime({timezone:"Europe/Brussels"})`. + Such calls return the current clock time. If you need the previous behaviour, + then explicitly state one or more numeric fields as `0`, e.g, + `datetime({year: 0, timezone:"Europe/Brussels"}`. + [#3339](https://github.com/memgraph/memgraph/pull/3339) + +{

🐞 Bug fixes

} + +- Fixed `convert_c.to_tree()` memory leak. Using `to_tree` will not indefinably + increase the memory. [#3333](https://github.com/memgraph/memgraph/pull/3333) +- Fixed an issue where `SHOW PRIVILEGES` ignored the target user's database + access rights. The `SHOW PRIVILEGES` now works correctly and will return an + empty result if the user does not have access to the target database. + [#3340](https://github.com/memgraph/memgraph/pull/3340) +- Fixed a cache invalidation bug that would cause the IN LIST operator to + produce wrong results. + [#3342](https://github.com/memgraph/memgraph/pull/3342) +- Fixed `datetime()` calls with only a `timezone` parameter (e.g., + `datetime({timezone:"Europe/Brussels"})`) to return the current clock time, + instead of a time with all numeric fields set to their minimum value. + [#3339](https://github.com/memgraph/memgraph/pull/3339) + +### MAGE v3.6.1 - October 16th, 2025 + +{

✨ New features

} + +- Added `embedding` module, allowing users to compute sentence embeddings for + vertices on CPU or Nvidia GPU. + [#662](https://github.com/memgraph/mage/pull/662). + +### Lab v3.6.1 - October 17th, 2025 + + + + +## Previous releases + ### Memgraph v3.6.0 - October 8th, 2025 {

⚠️ Breaking changes

} @@ -194,10 +235,10 @@ troubleshoot in production. - Fixed closing of database connections after migrations are completed. [#665](https://github.com/memgraph/mage/pull/665) - + ### Lab v3.6.0 - October 8th, 2025 -## Previous releases + ### Memgraph v3.5.2 - September 24th, 2025 diff --git a/public/pages/data-visualization/features/graphchat/graphchat-model-prompt.png b/public/pages/data-visualization/features/graphchat/graphchat-model-prompt.png new file mode 100644 index 000000000..c63ea05bd Binary files /dev/null and b/public/pages/data-visualization/features/graphchat/graphchat-model-prompt.png differ diff --git a/public/pages/data-visualization/features/graphchat/mcp-create-memgraph.png b/public/pages/data-visualization/features/graphchat/mcp-create-memgraph.png new file mode 100644 index 000000000..8a5cdbaa0 Binary files /dev/null and b/public/pages/data-visualization/features/graphchat/mcp-create-memgraph.png differ diff --git a/public/pages/data-visualization/features/graphchat/mcp-create-tavily.png b/public/pages/data-visualization/features/graphchat/mcp-create-tavily.png new file mode 100644 index 000000000..3f2aceecd Binary files /dev/null and b/public/pages/data-visualization/features/graphchat/mcp-create-tavily.png differ diff --git a/public/pages/data-visualization/features/graphchat/mcp-servers-settings.png b/public/pages/data-visualization/features/graphchat/mcp-servers-settings.png new file mode 100644 index 000000000..b001d117a Binary files /dev/null and b/public/pages/data-visualization/features/graphchat/mcp-servers-settings.png differ diff --git a/public/pages/data-visualization/features/graphchat/toolkit-builtin.png b/public/pages/data-visualization/features/graphchat/toolkit-builtin.png new file mode 100644 index 000000000..c73359911 Binary files /dev/null and b/public/pages/data-visualization/features/graphchat/toolkit-builtin.png differ diff --git a/public/pages/data-visualization/features/graphchat/toolkit-custom.png b/public/pages/data-visualization/features/graphchat/toolkit-custom.png new file mode 100644 index 000000000..3ef401f2c Binary files /dev/null and b/public/pages/data-visualization/features/graphchat/toolkit-custom.png differ diff --git a/public/pages/data-visualization/features/graphchat/toolkit-mcp.png b/public/pages/data-visualization/features/graphchat/toolkit-mcp.png new file mode 100644 index 000000000..0ac477bae Binary files /dev/null and b/public/pages/data-visualization/features/graphchat/toolkit-mcp.png differ diff --git a/public/pages/data-visualization/lab-user-manual/connection-types/conn-type-ha-cluster-input.png b/public/pages/data-visualization/lab-user-manual/connection-types/conn-type-ha-cluster-input.png index 5a0644bf5..701a27b58 100644 Binary files a/public/pages/data-visualization/lab-user-manual/connection-types/conn-type-ha-cluster-input.png and b/public/pages/data-visualization/lab-user-manual/connection-types/conn-type-ha-cluster-input.png differ diff --git a/public/pages/data-visualization/lab-user-manual/connection-types/conn-type-standalone-input.png b/public/pages/data-visualization/lab-user-manual/connection-types/conn-type-standalone-input.png index 73bd78b30..085692574 100644 Binary files a/public/pages/data-visualization/lab-user-manual/connection-types/conn-type-standalone-input.png and b/public/pages/data-visualization/lab-user-manual/connection-types/conn-type-standalone-input.png differ diff --git a/public/pages/data-visualization/lab-user-manual/graph-search-bar.png b/public/pages/data-visualization/lab-user-manual/graph-search-bar.png new file mode 100644 index 000000000..85adee555 Binary files /dev/null and b/public/pages/data-visualization/lab-user-manual/graph-search-bar.png differ diff --git a/public/pages/memgraph-in-production/benchmarking-memgraph/benchgraph-snippet.png b/public/pages/deployment/benchmarking-memgraph/benchgraph-snippet.png similarity index 100% rename from public/pages/memgraph-in-production/benchmarking-memgraph/benchgraph-snippet.png rename to public/pages/deployment/benchmarking-memgraph/benchgraph-snippet.png diff --git a/public/pages/memgraph-in-production/benchmarking-memgraph/realistic-workload.png b/public/pages/deployment/benchmarking-memgraph/realistic-workload.png similarity index 100% rename from public/pages/memgraph-in-production/benchmarking-memgraph/realistic-workload.png rename to public/pages/deployment/benchmarking-memgraph/realistic-workload.png diff --git a/public/sitemap.xml b/public/sitemap.xml index 3cdd350b5..47033ee35 100644 --- a/public/sitemap.xml +++ b/public/sitemap.xml @@ -1,293 +1,294 @@ -https://memgraph.com/docs2025-08-28T08:11:23.942Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/algo2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/betweenness_centrality2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/betweenness_centrality_online2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/biconnected_components2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/bipartite_matching2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/bridges2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/collections2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/community_detection2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/community_detection_online2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/convert2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/convert_c2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/create2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/csv_utils2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/cugraph2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/cycles2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/date2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/degree_centrality2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/distance_calculator2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/do2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/elasticsearch_synchronization2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/export_util2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/gnn_link_prediction2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/gnn_node_classification2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/graph_analyzer2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/graph_coloring2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/graph_util2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/igraphalg2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/import_util2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/json_util2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/katz_centrality2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/katz_centrality_online2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/kmeans_clustering2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/label2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/leiden_community_detection2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/llm_util2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/map2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/math2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/max_flow2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/merge2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/meta2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/meta_util2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/mgps2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/migrate2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/neighbors2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/node2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/node2vec2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/node2vec_online2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/node_similarity2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/nodes2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/nxalg2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/pagerank2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/pagerank_online2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/path2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/periodic2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/refactor2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/set_cover2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/set_property2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/temporal2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/text2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/tgn2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/tsp2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/union_find2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/util_module2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/uuid_generator2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/vrp2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/weakly_connected_components2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/available-algorithms/xml_module2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/deep-path-traversal2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/install-mage2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/run-algorithms2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/advanced-algorithms/utilize-networkx2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/ai-ecosystem2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/ai-ecosystem/graph-rag2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/ai-ecosystem/graph-rag/examples-and-demos2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/ai-ecosystem/graph-rag/knowledge-graph-creation2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/ai-ecosystem/graph-rag/knowledge-retrieval2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/ai-ecosystem/graph-rag/prerequisites2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/ai-ecosystem/integrations2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/ai-ecosystem/machine-learning2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/client-libraries2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/client-libraries/c-sharp2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/client-libraries/go2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/client-libraries/graphql2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/client-libraries/java2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/client-libraries/javascript2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/client-libraries/nodejs2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/client-libraries/php2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/client-libraries/python2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/client-libraries/rust2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/clustering2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/clustering/high-availability2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/clustering/replication2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/clustering/replication/system-replication2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/coming-soon2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/custom-query-modules2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/custom-query-modules/c2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/custom-query-modules/c/c-api2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/custom-query-modules/c/c-example2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/custom-query-modules/contributing2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/custom-query-modules/cpp2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/custom-query-modules/cpp/cpp-api2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/custom-query-modules/cpp/cpp-example2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/custom-query-modules/manage-query-modules2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/custom-query-modules/python2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/custom-query-modules/python/implement-custom-query-module-in-python2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/custom-query-modules/python/mock-python-api2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/custom-query-modules/python/python-api2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/custom-query-modules/python/python-example2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/custom-query-modules/python/understanding-music-with-modules2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/custom-query-modules/rust2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/custom-query-modules/rust/rust-api2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/custom-query-modules/rust/rust-example2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-migration2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-migration/best-practices2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-migration/csv2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-migration/cypherl2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-migration/export-data2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-migration/json2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-migration/migrate-from-neo4j2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-migration/migrate-from-neo4j-using-single-cypher-query2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-migration/migrate-from-rdbms2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-migration/migrate-from-rdbms-directly2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-migration/migrate-iceberg-tables-from-data-lake-using-dremio2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-migration/migrate-memgraph-platform2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-migration/migrate-with-apache-spark2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-modeling2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-modeling/best-practices2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-modeling/graph-data-model2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-modeling/graph-data-model/lpg-vs-rdf2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-modeling/modeling-guides2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-modeling/modeling-guides/model-a-graph-from-csv-file2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-modeling/modeling-guides/model-a-knowledge-graph2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-streams2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-streams/graph-stream-processing-with-kafka2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-streams/kafka2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-streams/manage-streams-query2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-streams/transformation-modules2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-streams/transformation-modules/c-api2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/data-streams/transformation-modules/python-api2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management/authentication-and-authorization2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management/authentication-and-authorization/auth-system-integrations2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management/authentication-and-authorization/impersonate-user2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management/authentication-and-authorization/multiple-roles2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management/authentication-and-authorization/role-based-access-control2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management/authentication-and-authorization/user-profiles2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management/authentication-and-authorization/users2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management/backup-and-restore2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management/configuration2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management/debugging2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management/enabling-memgraph-enterprise2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management/experimental-features2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management/logs2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management/monitoring2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management/multi-tenancy2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management/query-metadata2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management/server-stats2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management/ssl-encryption2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/database-management/system-configuration2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/deployment2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/deployment/benchmarking-memgraph2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/deployment/best-practices2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/deployment/environments2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/deployment/environments/aws2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/deployment/environments/azure2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/deployment/environments/docker2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/deployment/environments/gcp2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/deployment/environments/linux2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/deployment/workloads2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/deployment/workloads/memgraph-in-cybersecurity2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/deployment/workloads/memgraph-in-graphrag2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/deployment/workloads/memgraph-in-high-throughput-workloads2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/fundamentals2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/fundamentals/constraints2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/fundamentals/data-durability2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/fundamentals/data-types2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/fundamentals/indexes2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/fundamentals/storage-access2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/fundamentals/storage-memory-usage2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/fundamentals/telemetry2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/fundamentals/transactions2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/fundamentals/triggers2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/getting-started2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/getting-started/build-memgraph-from-source2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/getting-started/cli2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/getting-started/first-steps-with-docker2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/getting-started/install-memgraph2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/getting-started/install-memgraph/amazon-linux2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/getting-started/install-memgraph/centos2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/getting-started/install-memgraph/debian2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/getting-started/install-memgraph/direct-download-links2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/getting-started/install-memgraph/docker2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/getting-started/install-memgraph/docker-compose2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/getting-started/install-memgraph/fedora2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/getting-started/install-memgraph/kubernetes2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/getting-started/install-memgraph/memgraph-cloud2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/getting-started/install-memgraph/redhat2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/getting-started/install-memgraph/rocky2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/getting-started/install-memgraph/ubuntu2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/getting-started/install-memgraph/wsl2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/help-center2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/help-center/errors2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/help-center/errors/auth2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/help-center/errors/connection2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/help-center/errors/durability2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/help-center/errors/high-availability2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/help-center/errors/memory2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/help-center/errors/modules2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/help-center/errors/ports2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/help-center/errors/python-modules2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/help-center/errors/replication2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/help-center/errors/snapshots2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/help-center/errors/socket2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/help-center/errors/ssl2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/help-center/errors/transactions2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/help-center/errors/unknown2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/help-center/faq2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/configuration2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features/collections2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features/csv-file-import2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features/custom-configuration2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features/graph-schema2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features/graph-style-script2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features/graph-style-script/built-in-elements2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features/graph-style-script/directive-properties2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features/graph-style-script/main-building-blocks2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features/graph-style-script/style-your-graphs-in-memgraph-lab2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features/graphchat2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features/layout2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features/logs2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features/monitoring2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features/multi-tenancy2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features/query-modules2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features/run-history2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features/sharing-features2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features/single-sign-on2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/features/streams2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/getting-started2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/getting-started/connection-types2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/getting-started/data-migration2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/getting-started/installation-and-deployment2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/memgraph-lab/querying2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/best-practices2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/alter2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/call2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/case2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/create2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/delete2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/drop-graph2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/explain2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/foreach2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/load-csv2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/match2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/merge2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/optional-match2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/profile2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/remove2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/return2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/set2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/union2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/unwind2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/where2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/clauses/with2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/create-graph-objects2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/differences-in-cypher-implementations2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/exploring-datasets2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/exploring-datasets/analyzing-ted-talks2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/exploring-datasets/backpacking-through-europe2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/exploring-datasets/exploring-the-european-road-network2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/exploring-datasets/football-transfers2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/exploring-datasets/got-deaths2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/exploring-datasets/graphing-the-premier-league2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/exploring-datasets/marvel-universe2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/exploring-datasets/movie-recommendation2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/expressions2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/functions2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/query-plan2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/read-and-modify-data2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/schema2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/text-search2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/time-to-live2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/querying/vector-search2025-08-28T08:11:23.943Zdaily0.7 -https://memgraph.com/docs/release-notes2025-08-28T08:11:23.943Zdaily0.7 +https://memgraph.com/docs2025-10-09T10:12:12.537Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/algo2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/betweenness_centrality2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/betweenness_centrality_online2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/biconnected_components2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/bipartite_matching2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/bridges2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/collections2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/community_detection2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/community_detection_online2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/convert2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/convert_c2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/create2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/csv_utils2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/cugraph2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/cycles2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/date2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/degree_centrality2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/distance_calculator2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/do2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/elasticsearch_synchronization2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/export_util2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/gnn_link_prediction2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/gnn_node_classification2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/graph_analyzer2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/graph_coloring2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/graph_util2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/igraphalg2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/import_util2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/json_util2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/katz_centrality2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/katz_centrality_online2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/kmeans_clustering2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/label2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/leiden_community_detection2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/llm_util2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/map2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/math2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/max_flow2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/merge2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/meta2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/meta_util2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/mgps2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/migrate2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/neighbors2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/node2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/node2vec2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/node2vec_online2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/node_similarity2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/nodes2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/nxalg2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/pagerank2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/pagerank_online2025-10-09T10:12:12.538Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/path2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/periodic2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/refactor2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/set_cover2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/set_property2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/temporal2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/text2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/tgn2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/tsp2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/union_find2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/util_module2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/uuid_generator2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/vrp2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/weakly_connected_components2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/available-algorithms/xml_module2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/deep-path-traversal2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/install-mage2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/run-algorithms2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/advanced-algorithms/utilize-networkx2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/ai-ecosystem2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/ai-ecosystem/graph-rag2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/ai-ecosystem/graph-rag/examples-and-demos2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/ai-ecosystem/graph-rag/knowledge-graph-creation2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/ai-ecosystem/graph-rag/knowledge-retrieval2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/ai-ecosystem/graph-rag/prerequisites2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/ai-ecosystem/integrations2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/ai-ecosystem/machine-learning2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/client-libraries2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/client-libraries/c-sharp2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/client-libraries/go2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/client-libraries/graphql2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/client-libraries/java2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/client-libraries/javascript2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/client-libraries/nodejs2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/client-libraries/php2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/client-libraries/python2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/client-libraries/rust2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/clustering2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/clustering/high-availability2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/clustering/replication2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/clustering/replication/system-replication2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/coming-soon2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/custom-query-modules2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/custom-query-modules/c2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/custom-query-modules/c/c-api2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/custom-query-modules/c/c-example2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/custom-query-modules/contributing2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/custom-query-modules/cpp2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/custom-query-modules/cpp/cpp-api2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/custom-query-modules/cpp/cpp-example2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/custom-query-modules/manage-query-modules2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/custom-query-modules/python2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/custom-query-modules/python/implement-custom-query-module-in-python2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/custom-query-modules/python/mock-python-api2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/custom-query-modules/python/python-api2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/custom-query-modules/python/python-example2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/custom-query-modules/python/understanding-music-with-modules2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/custom-query-modules/rust2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/custom-query-modules/rust/rust-api2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/custom-query-modules/rust/rust-example2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-migration2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-migration/best-practices2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-migration/csv2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-migration/cypherl2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-migration/export-data2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-migration/json2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-migration/migrate-from-neo4j2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-migration/migrate-from-neo4j-using-single-cypher-query2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-migration/migrate-from-rdbms2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-migration/migrate-from-rdbms-directly2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-migration/migrate-iceberg-tables-from-data-lake-using-dremio2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-migration/migrate-memgraph-platform2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-migration/migrate-with-apache-spark2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-modeling2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-modeling/best-practices2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-modeling/graph-data-model2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-modeling/graph-data-model/lpg-vs-rdf2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-modeling/modeling-guides2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-modeling/modeling-guides/model-a-graph-from-csv-file2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-modeling/modeling-guides/model-a-knowledge-graph2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-streams2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-streams/graph-stream-processing-with-kafka2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-streams/kafka2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-streams/manage-streams-query2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-streams/transformation-modules2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-streams/transformation-modules/c-api2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/data-streams/transformation-modules/python-api2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management/authentication-and-authorization2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management/authentication-and-authorization/auth-system-integrations2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management/authentication-and-authorization/impersonate-user2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management/authentication-and-authorization/multiple-roles2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management/authentication-and-authorization/role-based-access-control2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management/authentication-and-authorization/user-profiles2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management/authentication-and-authorization/users2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management/backup-and-restore2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management/configuration2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management/debugging2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management/enabling-memgraph-enterprise2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management/experimental-features2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management/logs2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management/monitoring2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management/multi-tenancy2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management/query-metadata2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management/server-stats2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management/ssl-encryption2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/database-management/system-configuration2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/deployment2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/deployment/benchmarking-memgraph2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/deployment/best-practices2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/deployment/environments2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/deployment/environments/aws2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/deployment/environments/azure2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/deployment/environments/docker2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/deployment/environments/gcp2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/deployment/environments/linux2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/deployment/workloads2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/deployment/workloads/memgraph-in-cybersecurity2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/deployment/workloads/memgraph-in-graphrag2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/deployment/workloads/memgraph-in-high-throughput-workloads2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/fundamentals2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/fundamentals/constraints2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/fundamentals/data-durability2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/fundamentals/data-types2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/fundamentals/indexes2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/fundamentals/storage-access2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/fundamentals/storage-memory-usage2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/fundamentals/telemetry2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/fundamentals/transactions2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/fundamentals/triggers2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/getting-started2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/getting-started/build-memgraph-from-source2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/getting-started/cli2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/getting-started/first-steps-with-docker2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/getting-started/install-memgraph2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/getting-started/install-memgraph/amazon-linux2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/getting-started/install-memgraph/centos2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/getting-started/install-memgraph/debian2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/getting-started/install-memgraph/direct-download-links2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/getting-started/install-memgraph/docker2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/getting-started/install-memgraph/docker-compose2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/getting-started/install-memgraph/fedora2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/getting-started/install-memgraph/kubernetes2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/getting-started/install-memgraph/memgraph-cloud2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/getting-started/install-memgraph/redhat2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/getting-started/install-memgraph/rocky2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/getting-started/install-memgraph/ubuntu2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/getting-started/install-memgraph/wsl2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/help-center2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/help-center/errors2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/help-center/errors/auth2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/help-center/errors/connection2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/help-center/errors/durability2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/help-center/errors/high-availability2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/help-center/errors/memory2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/help-center/errors/modules2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/help-center/errors/ports2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/help-center/errors/python-modules2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/help-center/errors/replication2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/help-center/errors/snapshots2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/help-center/errors/socket2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/help-center/errors/ssl2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/help-center/errors/transactions2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/help-center/errors/unknown2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/help-center/faq2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/configuration2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/collections2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/csv-file-import2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/custom-configuration2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/data-modeling2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/graph-schema2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/graph-style-script2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/graph-style-script/built-in-elements2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/graph-style-script/directive-properties2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/graph-style-script/main-building-blocks2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/graph-style-script/style-your-graphs-in-memgraph-lab2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/graphchat2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/layout2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/logs2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/monitoring2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/multi-tenancy2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/query-modules2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/run-history2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/sharing-features2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/single-sign-on2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/features/streams2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/getting-started2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/getting-started/connection-types2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/getting-started/data-migration2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/getting-started/installation-and-deployment2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/memgraph-lab/querying2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/best-practices2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/alter2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/call2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/case2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/create2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/delete2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/drop2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/explain2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/foreach2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/load-csv2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/match2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/merge2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/optional-match2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/profile2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/remove2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/return2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/set2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/union2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/unwind2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/where2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/clauses/with2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/create-graph-objects2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/differences-in-cypher-implementations2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/exploring-datasets2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/exploring-datasets/analyzing-ted-talks2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/exploring-datasets/backpacking-through-europe2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/exploring-datasets/exploring-the-european-road-network2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/exploring-datasets/football-transfers2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/exploring-datasets/got-deaths2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/exploring-datasets/graphing-the-premier-league2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/exploring-datasets/marvel-universe2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/exploring-datasets/movie-recommendation2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/expressions2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/functions2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/query-plan2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/read-and-modify-data2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/schema2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/text-search2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/time-to-live2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/querying/vector-search2025-10-09T10:12:12.539Zdaily0.7 +https://memgraph.com/docs/release-notes2025-10-09T10:12:12.539Zdaily0.7 \ No newline at end of file