AWS neptune-analytics documentation change
Summary
Added vertexLabels parameter documentation for node filtering in Louvain algorithm, updated concurrency limitation description
Security assessment
The changes add optional node filtering capabilities and clarify concurrency limits. While this improves functionality and clarifies usage constraints, there is no evidence of addressing security vulnerabilities or introducing security-specific features.
Diff
diff --git a/neptune-analytics/latest/userguide/louvain.md b/neptune-analytics/latest/userguide/louvain.md index 6702f030a..14c0c5fb3 100644 --- a//neptune-analytics/latest/userguide/louvain.md +++ b//neptune-analytics/latest/userguide/louvain.md @@ -47 +47 @@ The Louvain algorithm is particularly useful in these cases because it: - * Louvain is only allowed to run globally. + * There can only be one Louvain algorithm call running at a time. @@ -59,0 +60 @@ The Louvain algorithm is particularly useful in these cases because it: + vertexLabels: [list of vertex labels for filtering (optional)], @@ -80,0 +82,4 @@ The node or nodes for which the algorithm will return the computed community ids + * **vertexLabels** _(optional)_ – _type:_ `a list of vertex label strings; example ["airport", ...]`; _default: no vertex filtering_. + +Node labels for node filtering. To filter on one or more vertex labels, provide a list of node labels. Vertices matching any label in the vertexLabels list are the only vertices that are passed to the algorithm computation. If no vertexLabels field is provided then all vertices are passed to the Louvain algorithm. + @@ -140,0 +146 @@ Unweighted example: + vertexLabels: ["airport"], @@ -156,0 +163 @@ Sample use case: you may want to identify natural communities of stops where the + vertexLabels: ["airport"], @@ -173,0 +181 @@ This is a query integration example, where `.louvain` uses the output of a prece + vertexLabels: ["airport"],