AWS neptune-analytics documentation change
Summary
Corrected grammar ('result a' to 'result in') and improved warning about query output size with unrestricted MATCH(n).
Security assessment
Enhances clarity of performance warnings but does not address security issues or document security features. Focuses on query efficiency best practices.
Diff
diff --git a/neptune-analytics/latest/userguide/sssp-deltaStepping-path.md b/neptune-analytics/latest/userguide/sssp-deltaStepping-path.md index b632f4fb1..eebfbcae1 100644 --- a//neptune-analytics/latest/userguide/sssp-deltaStepping-path.md +++ b//neptune-analytics/latest/userguide/sssp-deltaStepping-path.md @@ -155 +155 @@ This is a query integration example, where `.sssp.deltaStepping.path` follows a -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.