AWS neptune-analytics documentation change
Summary
Fixed typo in performance warning and improved clarity of query execution caveat
Security assessment
The change emphasizes query performance best practices but does not address security vulnerabilities or introduce security features.
Diff
diff --git a/neptune-analytics/latest/userguide/egonet-edgelist.md b/neptune-analytics/latest/userguide/egonet-edgelist.md index e3100d4d4..d1cbdc081 100644 --- a//neptune-analytics/latest/userguide/egonet-edgelist.md +++ b//neptune-analytics/latest/userguide/egonet-edgelist.md @@ -140 +140 @@ This is a query integration example, where `.egonet.edgeList` follows a `MATCH` -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.