AWS neptune-analytics documentation change
Summary
Fixed typo ('up to'), corrected algorithm name spelling, and added LIMIT in query example
Security assessment
Typographical corrections and query example refinement. The LIMIT addition is a best practice for performance, not explicitly a security measure.
Diff
diff --git a/neptune-analytics/latest/userguide/page-rank.md b/neptune-analytics/latest/userguide/page-rank.md index c6006e934..78d426175 100644 --- a//neptune-analytics/latest/userguide/page-rank.md +++ b//neptune-analytics/latest/userguide/page-rank.md @@ -107 +107 @@ The additional inputs to the algorithm are a list of vertices to be personalized -Neptune Analytics allows up 8192 vertices in the personalization vector, sourceNodes. +Neptune Analytics allows up to 8192 vertices in the personalization vector, sourceNodes. @@ -185 +185 @@ The type of values associated with the edgeWeightProperty argument, specified as - * **sourceNodes** _(optional) - required if running personalized PageReank_ – _type:_ `list`; _default: none_. + * **sourceNodes** _(optional) - required if running personalized PageRank_ – _type:_ `list`; _default: none_. @@ -235 +235 @@ This is a standalone example, where the input vertex list is explicitly specifie -This is a query integration examples, where `.pageRank` follows a `MATCH` clause and uses frontier injection to take the output of the `MATCH` clause as its list of input nodes: +This is a query integration example, where `.pageRank` follows a `MATCH` clause and uses frontier injection to take the output of the `MATCH` clause as its list of input nodes: @@ -316 +316 @@ Here is an example of the output returned by .pageRank when run against the [ sa - --query-string "CALL neptune.algo.pageRank(n) YIELD node, rank RETURN node, rank LIMIT" \ + --query-string "CALL neptune.algo.pageRank(n) YIELD node, rank RETURN node, rank LIMIT 2" \