You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
=== Changing the store format of existing databases
122
122
123
-
<<<<<<< HEAD
124
-
Starting from 5.23, `block` format is the recommended format for Enterprise Edition due to its superior performance and scalability.
125
-
It uses advanced data structures and inlining techniques to enhance data locality, which leads to better resource utilization.
126
-
Therefore, it is highly recommended that Enterprise Edition users migrate all databases to `block` format at their earliest convenience to ensure the best possible performance.
127
-
`block` format is the default format for new databases created in 5.23 and later, and is the default format for all databases in 5.26 and later.
128
-
129
-
From 5.25 onwards, the `block` format supports token names (including node labels, property keys, and relationship type names) of any length up to the GQL identifier max length of 16,383 characters.
130
-
Thus, token names must adhere to this length limit when migrating from `aligned` to `block` format.
131
-
132
-
`standard` and `high_limit` formats are deprecated in 5.23 and will be removed in a future release.
133
-
For more information, see <<format-deprecations, Format deprecations>>.
134
-
=======
135
123
The `block` format is the default format for Enterprise Edition due to its superior performance and scalability.
136
124
Therefore, migrating all databases to `block` format is recommended to ensure optimal performance.
137
-
>>>>>>> eed2dd82 (remove and update many more mentions of 5.x)
Copy file name to clipboardExpand all lines: modules/ROOT/pages/index.adoc
-74Lines changed: 0 additions & 74 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,81 +15,7 @@ For all information on *upgrading and migrating Neo4j*, see the link:{neo4j-docs
15
15
For more information on link:https://neo4j.com/aura/[Aura], the Neo4j fully managed cloud service, see the link:{neo4j-docs-base-uri}/aura/[Aura] [Neo4j Aura Manual].
16
16
17
17
18
-
<<<<<<< HEAD
19
18
The latest version of Neo4j is *{neo4j-version-exact}*.
20
-
=======
21
-
== Documentation updates for Neo4j 5
22
-
23
-
* Restructured chapter on clustering.
24
-
+
25
-
The new clustering infrastructure decouples servers from databases, improving scalability and cloud-readiness.
26
-
As such, the documentation has been restructured and rewritten.
27
-
For a detailed description and instructions on how to set up clustering, see xref:clustering/index.adoc[Clustering].
28
-
29
-
* Composite databases.
30
-
+
31
-
Fabric technology is used to improve the setting and management of sharded and federated databases with dynamic compositions of databases.
32
-
A new surface to administer Fabric databases, named Composite databases, is new in 5.0.
33
-
Configuration settings have been removed and Composite databases are now administered via Cypher commands.
34
-
For more information, see the new chapter on xref:database-administration/composite-databases/concepts.adoc[Composite databases], which replaces the _Fabric_ chapter from previous versions.
35
-
36
-
* `neo4j-admin` refresh.
37
-
+
38
-
All admin functionalities have been consolidated into a single tool, and all commands have been grouped by scope.
39
-
There is an optional neo4j-admin conf file and individual conf files for each command so that there is more control over values provided for each command.
40
-
Improved features, more control, and a consistent set of arguments for the database administrator. +
41
-
See xref:tools/neo4j-admin/index.adoc[Neo4j Admin and Neo4j CLI] for details.
42
-
43
-
* A major overhaul of backup and restore.
44
-
+
45
-
The new backup subsystem provides:
46
-
47
-
** Full and differential backup to an immutable file, and aggregation to compile a chain of backups into a full backup.
48
-
** Differential backup reduces storage requirements and provides point-in-time restore on timestamps or transaction IDs.
49
-
** A new backup API for backup management and operability and target multiple URIs in a single backup command to support clusters.
50
-
51
-
* Incremental offline import.
52
-
+
53
-
The `neo4j-admin database import` command can now add more data to existing databases. +
54
-
xref:tools/neo4j-admin/neo4j-admin-import.adoc[Import chapter] has been updated.
55
-
You can find more details there.
56
-
57
-
* Log4j integration completion.
58
-
+
59
-
The logging framework is fully integrated with Log4j, providing more functionality and better control of all the database logs. +
60
-
Configuration settings are located in the `<NEO4J_HOME>/conf` folder in the _user-logs.xml_ used for _neo4j.log_ and _server-logs.xml_ used for _debug.log_, _security.log_, _http.log_, and _query.log_.
61
-
Query log uses the same format as _neo4j.log_. +
62
-
Users are able to use/modify Log4j XML files. +
63
-
See xref:monitoring/logging.adoc[the section on the logging mechanisms in Neo4j] for more details.
64
-
65
-
* Updates in the *Cypher Shell* section.
66
-
67
-
** Cypher Shell supports impersonation.
68
-
+
69
-
Cypher Shell users can impersonate other users via `--impersonate` or the command `:impersonate` (requires `IMPERSONATE` privileges). +
70
-
Visit xref:tools/cypher-shell.adoc[Cypher Shell page] for more details.
71
-
72
-
** Cypher Shell logging.
73
-
+
74
-
New option `--log` is introduced to enable Java Driver logging to the specified file.
75
-
When users report problems with Java Driver/Bolt, now they can use Cypher Shell to try and replicate the issue without having to edit the client app that uses the driver. +
76
-
You can find more information in the xref:tools/cypher-shell.adoc[Cypher Shell section].
77
-
78
-
* Immutable privileges.
79
-
+
80
-
Immutable roles and privileges are useful for restricting the actions of users who themselves are able to administer privileges. +
81
-
Cloud operators can use sidecar design pattern to control RBAC-based permissions. +
82
-
For more information, see xref:authentication-authorization/immutable-roles-privileges.adoc[Immutable roles and privileges].
83
-
84
-
* Changes to Neo4j indexes
85
-
** The B-tree index type has been removed.
86
-
** New Range and Point index types are available now.
87
-
** An improved index provider, `text-2.0`, for enhanced performance.
88
-
New Text indexes will use the `text-2.0` provider by default.
89
-
** Full-text indexes can now index lists of strings.
90
-
+
91
-
See xref:performance/index-configuration.adoc[Index configuration] for more details.
92
-
>>>>>>> eed2dd82 (remove and update many more mentions of 5.x)
0 commit comments