AWS neptune-analytics documentation change
Summary
Fixed a typo (explitly -> explicitly) and added a warning about using MATCH(n) without restrictions causing long-running queries.
Security assessment
The changes are typographical corrections and a performance warning. The warning advises using LIMIT or conditions to prevent long-running queries, which is about resource management and query efficiency, not security. No security vulnerability is mentioned.
Diff
diff --git a/neptune-analytics/latest/userguide/bfs-standard.md b/neptune-analytics/latest/userguide/bfs-standard.md index 75aec752f..24da96dbb 100644 --- a//neptune-analytics/latest/userguide/bfs-standard.md +++ b//neptune-analytics/latest/userguide/bfs-standard.md @@ -133 +133 @@ The examples below are query integration examples, where `.bfs` follows a `MATCH -The `MATCH` clause can also explitly specify a starting node list using the `id()` function, like this: +The `MATCH` clause can also explicitly specify a starting node list using the `id()` function, like this: @@ -151 +151 @@ Also: -It is not good practice to use `MATCH(n)` without restriction in query integrations. Keep in mind that every node returned by the `MATCH(n)` clause invokes the algorithm once, which can result a very long-running query if a large number of nodes is returned. Use `LIMIT` or put conditions on the `MATCH` clause to restrict its output appropriately. +It is not good practice to use `MATCH(n)` without restriction in query integrations. Keep in mind that every node returned by the `MATCH(n)` clause invokes the algorithm once, which can result in a very long-running query if a large number of nodes is returned. Use `LIMIT` or put conditions on the `MATCH` clause to restrict its output appropriately.