bolt+routing in Neo4j Browser

What drivers are used when

There are two kinds of Bolt drivers specified by URI scheme: the 'bolt://' scheme is used to create a direct driver and the 'bolt+routing://' scheme is used to create a routing driver. In Neo4j Browser, the bolt+routing setting is used to control which driver should be used. However it is not always appropriate for Neo4j Browser to use a routing driver even when bolt+routing is on.

Neo4j Browser will always:

  • use a direct driver for user administration frames
  • use a direct driver to populate sysinfo and the member specific items in the information panel e.g. version, cluster role etc

If bolt+routing is on and the provided URI points to a Core Causal Cluster member Neo4j Browser will:

  • use a routing driver for all cypher queries submitted via the editor (including calls to user admininstration procedures)
  • use a routing driver to populate the metadata (labels, relationship types, properties) in the information panel

If bolt+routing is off or the provided URI does not point to a Causal Cluster member or the provided URI points to a Read-Replica Causal Cluster member, Neo4j Browser will:

  • use a direct driver for all cypher queries submitted via the editor
  • use a direct driver to populate the metadata (labels, relationship types, properties) in the information panel

Please note that in order for bolt+routing to work correctly the current user must exist on all members in the cluster with the same authentication credentials.

Reference: Bolt drivers manual section
Related: :help bolt :help bolt encryption