AWS neptune-analytics documentation change
Summary
Improved warning about unrestricted MATCH(n) clauses by adding missing 'in' (from 'result a' to 'result in a')
Security assessment
Same performance-focused warning improvement as in closeness-centrality.md. No explicit security context provided regarding potential abuse or vulnerabilities.
Diff
diff --git a/neptune-analytics/latest/userguide/common-neighbors.md b/neptune-analytics/latest/userguide/common-neighbors.md index 7a7b293e8..67cc357d9 100644 --- a//neptune-analytics/latest/userguide/common-neighbors.md +++ b//neptune-analytics/latest/userguide/common-neighbors.md @@ -81 +81 @@ This example specifies multiple nodes. It returns a row for each combination of -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.