AWS neptune-analytics documentation change
Summary
Minor grammatical fix in timeout recommendation and corrected query syntax (lowercase 'Match' to 'MATCH')
Security assessment
The timeout clarification improves documentation accuracy but does not relate to a security flaw. The query syntax correction ensures proper execution but does not mitigate a security risk.
Diff
diff --git a/neptune-analytics/latest/userguide/louvain.md b/neptune-analytics/latest/userguide/louvain.md index ac54002d1..18ebc9ca3 100644 --- a//neptune-analytics/latest/userguide/louvain.md +++ b//neptune-analytics/latest/userguide/louvain.md @@ -49 +49 @@ The Louvain algorithm is particularly useful in these cases because it: - * Louvain is expected to run a long time, hence please set the query timeout to be large number to avoid query timeout. See [ query-timeout-milliseconds](https://docs.aws.amazon.com//neptune-analytics/latest/userguide/query-APIs-execute-query.html#query-APIs-execute-query-input) for more information on setting upper bounds on query run time. + * Louvain is expected to run a long time, hence please set the query timeout to be a large number to avoid query timeout. See [ query-timeout-milliseconds](https://docs.aws.amazon.com//neptune-analytics/latest/userguide/query-APIs-execute-query.html#query-APIs-execute-query-input) for more information on setting upper bounds on query run time. @@ -205 +205 @@ Here is an example of the output returned by .louvain when run against the [ sam - --query-string 'query=Match (n) \ + --query-string 'MATCH (n) \