AWS neptune-analytics documentation change
Summary
Fixed typo in performance warning about unrestricted MATCH clauses ('result a' → 'result in')
Security assessment
Change addresses query performance best practices without mentioning security vulnerabilities or protections. The warning focuses on preventing long-running queries rather than security risks.
Diff
diff --git a/neptune-analytics/latest/userguide/sssp-deltaStepping.md b/neptune-analytics/latest/userguide/sssp-deltaStepping.md index 134300219..acf778577 100644 --- a//neptune-analytics/latest/userguide/sssp-deltaStepping.md +++ b//neptune-analytics/latest/userguide/sssp-deltaStepping.md @@ -134 +134 @@ This is a query integration example, where where `.sssp.deltaStepping` 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 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.