AWS neptune-analytics documentation change
Summary
Fixed typos and improved grammar in documentation. Added clarification about restricting MATCH clauses with LIMIT/conditions to prevent long-running queries.
Security assessment
Changes are grammatical improvements and performance recommendations. No specific security vulnerability or weakness is addressed. The query restriction advice relates to performance optimization rather than security hardening.
Diff
diff --git a/neptune-analytics/latest/userguide/wcc.md b/neptune-analytics/latest/userguide/wcc.md index 3b1ede89b..61a840dc1 100644 --- a//neptune-analytics/latest/userguide/wcc.md +++ b//neptune-analytics/latest/userguide/wcc.md @@ -11 +11 @@ The Weakly Connected Components (WCC) algorithm finds the weakly-connected compo -Identifying weakly-conected components helps in understanding the overall connectivity and structure of the graph. Weakly-connected components can be used in transportation networks to identify disconnected regions that may require improved connectivity, and in social networks to find isolated groups of users with limited interactions, and in webpage analysis to pinpoint sections with low accessibility. +Identifying weakly-connected components helps in understanding the overall connectivity and structure of the graph. Weakly-connected components can be used in transportation networks to identify disconnected regions that may require improved connectivity, and in social networks to find isolated groups of users with limited interactions, and in webpage analysis to pinpoint sections with low accessibility. @@ -87 +87 @@ This is a standalone example, where the source node list is explicitly provided -This is a query integration examples, where `.wcc` follows a `MATCH` clause and uses the output of the MATCH clause as its source node list: +This is a query integration example, where `.wcc` follows a `MATCH` clause and uses the output of the MATCH clause as its source node list: @@ -103 +103 @@ This is a query integration examples, where `.wcc` follows a `MATCH` clause and -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.