AWS neptune-analytics documentation change
Summary
Corrected grammar ('result a' to 'result in') in warning about unrestricted MATCH(n) clauses causing long-running queries.
Security assessment
Grammatical improvement to existing performance guidance. No security context or security feature documentation added.
Diff
diff --git a/neptune-analytics/latest/userguide/sssp-bellmanFord-path.md b/neptune-analytics/latest/userguide/sssp-bellmanFord-path.md index 1f0e9a14d..24f003718 100644 --- a//neptune-analytics/latest/userguide/sssp-bellmanFord-path.md +++ b//neptune-analytics/latest/userguide/sssp-bellmanFord-path.md @@ -148 +148 @@ This is a query integration example, where `.sssp.bellmanFord.path` follows a `M -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 are returned; and that every source-target node pair produces an output, which can result in a very large query output if a large number of nodes are 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 are returned; and that every source-target node pair produces an output, which can result in a very large query output if a large number of nodes are returned. Use `LIMIT` or put conditions on the `MATCH` clause to restrict its output appropriately.