Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove mention of bolt+routing #185

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Remove mention of bolt+routing #185

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions articles/modules/ROOT/pages/how-neo4j-browser-bolt-routing.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,16 +1,16 @@
= How Neo4j Browser uses bolt+routing
= How Neo4j Browser uses the neo4j scheme
:slug: how-neo4j-browser-bolt-routing
:author: José Rocha
:neo4j-versions: 3.5, 4.0, 4.1, 4.2, 4.3, 4.4

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.
There are two kinds of Bolt drivers specified by URI scheme: the *bolt://* scheme is used to create a direct driver and the *neo4j://* scheme is used to create a routing driver.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm actually not sure when this was changed. Notice how the top of the entry specifies

:neo4j-versions: 3.5, 4.0, 4.1, 4.2, 4.3, 4.4

So I think this should rather be driver version specific vs. server version specific.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, this would be about the pre-4.x drivers.


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

When using bolt+routing and the provided URI points to a Core Causal Cluster member Neo4j Browser will:
When using the neo4j scheme 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
Expand All @@ -20,7 +20,7 @@ If the provided URI points to a Read-Replica Causal Cluster member, Neo4j Browse
- 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.
Please note that in order for the neo4j scheme to work correctly the current user must exist on all members in the cluster with the same authentication credentials.

== Troubleshooting

Expand Down