You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/modules/ROOT/pages/graph-object.adoc
+3-10Lines changed: 3 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -159,16 +159,7 @@ This in particular means that:
159
159
If multiple node dataframes are used, they need to contain distinct node ids across all node data frames.
160
160
* Prior to the `construct` call, a call to `GraphDataScience.set_database` must have been made to explicitly specify which Neo4j database should be targeted.
161
161
162
-
163
-
=== Limitations on community edition
164
-
165
-
For users of GDS community edition, `gds.graph.construct` leverages Cypher Aggregation in implementation.
166
-
This implies performance can be impacted for large graphs.
167
-
It is possible that socket connection with the database times out.
168
-
If this happens, a possible workaround is to modify the server configuration [https://neo4j.com/docs/operations-manual/current/configuration/configuration-settings/#config_server.bolt.connection_keep_alive]`server.bolt.connection_keep_alive`
169
-
or [https://neo4j.com/docs/operations-manual/current/configuration/configuration-settings/#config_server.bolt.connection_keep_alive_probes]`server.bolt.connection_keep_alive_probes`.
170
-
However, be aware of the side effects such as a genuine connection issue now taking longer to be detected.
@@ -287,6 +278,8 @@ The direction (`DIRECTED` or `UNDIRECTED`) of the relationships in the projected
287
278
If the given NetworkX graph is directed, so a (sub)class of either `networkx.DiGraph` or `networkx.MultiDiGraph`, the relationships will be `DIRECTED` in the projection.
For users of GDS community edition, performance can be impacted for large graphs.
4
+
It is possible that socket connection with the database times out.
5
+
If this happens, a possible workaround is to modify the server configuration https://neo4j.com/docs/operations-manual/current/configuration/configuration-settings/#config_server.bolt.connection_keep_alive[`server.bolt.connection_keep_alive`]
6
+
or https://neo4j.com/docs/operations-manual/current/configuration/configuration-settings/#config_server.bolt.connection_keep_alive_probes[`server.bolt.connection_keep_alive_probes`].
7
+
However, be aware of the side effects such as a genuine connection issue now taking longer to be detected.
0 commit comments