Skip to content

Commit

Permalink
update show settings tables(#877) (#879)
Browse files Browse the repository at this point in the history
Co-authored-by: Reneta Popova <reneta.popova@neo4j.com>
  • Loading branch information
JPryce-Aklundh and renetapopova authored Jan 31, 2024
1 parent 1c91823 commit a878c34
Showing 1 changed file with 4 additions and 32 deletions.
36 changes: 4 additions & 32 deletions modules/ROOT/pages/clauses/listing-settings.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -183,15 +183,15 @@ For a full list of all available settings in Neo4j, refer to link:{neo4j-docs-ba
== Listing settings with filtering on output columns

The listed settings can be filtered by using the `WHERE` clause.
For example, the following query returns the name, value, and description of all settings starting with 'dbms':
For example, the following query returns the name, value, and description of the first three settings starting with 'dbms':

.Query
[source, cypher]
----
SHOW SETTINGS YIELD name, value, description
WHERE name STARTS WITH 'dbms'
RETURN name, value, description
LIMIT 10
LIMIT 3
----

.Result
Expand All @@ -211,38 +211,9 @@ LIMIT 10
| "WARN"
| "The level of middleware logging"

| "dbms.cluster.discovery.resolver_type"
| "LIST"
| "Configure the discovery type used for cluster name resolution"

| "dbms.cluster.discovery.type"
| "LIST"
| "This setting has been replaced by 'dbms.cluster.discovery.resolver_type'"

| "dbms.cluster.minimum_initial_system_primaries_count"
| "3"
| "Minimum number of machines initially required to formed a clustered DBMS. The cluster is considered formed when at least this many members have discovered each other, bound together and bootstrapped a highly available system database. As a result, at least this many of the cluster's initial machines must have 'server.cluster.system_database_mode' set to 'PRIMARY'.NOTE: If 'dbms.cluster.discovery.resolver_type' is set to 'LIST' and 'dbms.cluster.discovery.endpoints' is empty then the user is assumed to be deploying a standalone DBMS, and the value of this setting is ignored."

| "dbms.cluster.network.handshake_timeout"
| "20s"
| "Time out for protocol negotiation handshake."

| "dbms.cluster.network.max_chunk_size"
| "32768"
| "Maximum chunk size allowable across network by clustering machinery."

| "dbms.cluster.network.supported_compression_algos"
| ""
| "Network compression algorithms that this instance will allow in negotiation as a comma-separated list. Listed in descending order of preference for incoming connections. An empty list implies no compression. For outgoing connections this merely specifies the allowed set of algorithms and the preference of the remote peer will be used for making the decision. Allowable values: [Gzip, Snappy, Snappy_validating, LZ4, LZ4_high_compression, LZ_validating, LZ4_high_compression_validating]"

| "dbms.cluster.raft.binding_timeout"
| "1d"
| "The time allowed for a database on a Neo4j server to either join a cluster or form a new cluster with at least the quorum of the members available. The members are provided by `dbms.cluster.discovery.endpoints` for the system database and by the topology graph for user databases."

3+d|Rows: 10
3+d|Rows: 3
|===


== Listing specific settings

It is possible to specify which settings to return in the list by setting names.
Expand All @@ -253,6 +224,7 @@ It is possible to specify which settings to return in the list by setting names.
SHOW SETTINGS "server.bolt.enabled", "server.bolt.advertised_address", "server.bolt.listen_address"
----


.Result
[role="queryresult",options="header,footer",cols="2m,1m,1m,1m,3m"]
|===
Expand Down

0 comments on commit a878c34

Please sign in to comment.