Skip to content

removed section on connecting to a rr #774

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

Merged
merged 1 commit into from
May 11, 2023
Merged

removed section on connecting to a rr #774

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
58 changes: 29 additions & 29 deletions modules/ROOT/pages/clustering/deploy.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
[role=enterprise-edition]
[[causal-clustering-deploy]]
= Deploy a cluster
:description: How to deploy a new Neo4j Causal Cluster.
:description: How to deploy a new Neo4j Causal Cluster.


[[causal-clustering-new-cluster-introduction]]
Expand Down Expand Up @@ -204,31 +204,31 @@ A way to ensure that a Read Replica contains a snapshot of a database in the clu
See xref:reference/procedures.adoc#procedure_dbms_cluster_readreplicatoggle[`dbms.cluster.readReplicaToggle()`] for more information.
====

[[causal-clustering-connect-to-a-read-replica]]
== Connect to a Read Replica

It is important to use the correct URI scheme when connecting to a Read Replica since it only allows read sessions/transactions.
The following table illustrates the supported URI schemes (the `+s` indicates that TLS has been configured for the cluster):

[cols="4", options="header"]
|===
|
| `bolt+s://`
| `neo4j+s://` read session/tx
| `neo4j+s://` write session/tx

| Cypher Shell
| {check-mark}
| {cross-mark}
| {cross-mark}

| Browser
| {check-mark}
| {cross-mark}
| {cross-mark}

| Neo4j Driver
| {check-mark}
| {check-mark}
| {cross-mark}
|===
// [[causal-clustering-connect-to-a-read-replica]]
// == Connect to a Read Replica

// It is important to use the correct URI scheme when connecting to a Read Replica since it only allows read sessions/transactions.
// The following table illustrates the supported URI schemes (the `+s` indicates that TLS has been configured for the cluster):

// [cols="4", options="header"]
// |===
// |
// | `bolt+s://`
// | `neo4j+s://` read session/tx
// | `neo4j+s://` write session/tx

// | Cypher Shell
// | {check-mark}
// | {cross-mark}
// | {cross-mark}

// | Browser
// | {check-mark}
// | {cross-mark}
// | {cross-mark}

// | Neo4j Driver
// | {check-mark}
// | {check-mark}
// | {cross-mark}
// |===