Skip to content

Commit 1159863

Browse files
vnickolovs1ckFlorentinD
committed
Update the sampled WCC example
Co-authored-by: Martin Junghanns <martin.junghanns@neotechnology.com> Co-authored-by: Florentin Dörre <florentin.dorre@neotechnology.com>
1 parent 5158683 commit 1159863

File tree

1 file changed

+5
-5
lines changed
  • doc/modules/ROOT/pages/algorithms

1 file changed

+5
-5
lines changed

doc/modules/ROOT/pages/algorithms/wcc.adoc

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -631,7 +631,7 @@ This time, we execute WCC on `myIndexedGraph` which will allow the algorithm to
631631
.The following will run the algorithm with sampled strategy and stream results:
632632
[source, cypher, role=noplay]
633633
----
634-
CALL gds.wcc.stream('myIndexedGraph')
634+
CALL gds.wcc.stream('myIndexedGraph', { consecutiveIds: true })
635635
YIELD nodeId, componentId
636636
RETURN gds.util.asNode(nodeId).name AS name, componentId
637637
ORDER BY componentId, name
@@ -644,11 +644,11 @@ ORDER BY componentId, name
644644
| "Alice" | 0
645645
| "Bridget" | 0
646646
| "Charles" | 0
647-
| "Doug" | 3
648-
| "Mark" | 3
649-
| "Michael" | 3
647+
| "Doug" | 1
648+
| "Mark" | 1
649+
| "Michael" | 1
650650
|===
651651
--
652652

653-
As expected, the results are the same as before.
653+
Here we also demonstrate the use of `conscutiveIds: true`, the results are semantically the same as before.
654654
However, on larger graphs, there will be a notable improvement in compute time.

0 commit comments

Comments
 (0)