AWS neptune-analytics documentation change
Summary
Fixed grammatical error in warning about unrestricted MATCH clauses causing long-running queries
Security assessment
The change corrects a grammatical error ('result a' to 'result in') but does not introduce or modify security-related content. The warning about query performance is operational, not directly addressing a security vulnerability.
Diff
diff --git a/neptune-analytics/latest/userguide/label-propagation.md b/neptune-analytics/latest/userguide/label-propagation.md index 330aff605..e6d16450c 100644 --- a//neptune-analytics/latest/userguide/label-propagation.md +++ b//neptune-analytics/latest/userguide/label-propagation.md @@ -152 +152 @@ This is a query integration example, where `.labelPropagation` uses the output o -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.