View Source Bolt.Sips.Router (Boltx v0.0.1)
This "driver" works in tandem with Neo4j's Causal Clustering feature by directing read and write behaviour to appropriate cluster members
Summary
Functions
Returns a specification to start this module under a supervisor.
parse the version string received from the server, while considering the lack of the patch number in some situations
start a new (DB)Connection process, supervised registered under a name following this convention
Functions
Returns a specification to start this module under a supervisor.
See Supervisor
.
merge_connections_maps(current_connections, new_connections, prefix \\ :default)
View Sourceparse the version string received from the server, while considering the lack of the patch number in some situations
Examples
iex> Bolt.Sips.Router.parse_server_version(%{"server" => "Neo4j/3.5.0"}) {"Neo4j/3.5.0", "3.5.0"}
iex> Bolt.Sips.Router.parse_server_version(%{"server" => "Neo4j/3.5"}) {"Neo4j/3.5", "3.5.0"}
iex> Bolt.Sips.Router.parse_server_version(%{"server" => "Neo4j/3.5.10"}) {"Neo4j/3.5.10", "3.5.10"}
iex> Bolt.Sips.Router.parse_server_version(%{"server" => "Neo4j/3.5.11.1"}) {"Neo4j/3.5.11.1", "3.5.11"}
start a new (DB)Connection process, supervised registered under a name following this convention:
- "role@hostname:port", the
role
,hostname
and theport
are collected from the user's configuration:opts
. Therole
parameter is ignored when therouting_table
parameter represents a neo4j map containing the definition for a neo4j cluster! It defaults to::direct
, when not specified!