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
Copy file name to clipboardExpand all lines: modules/ROOT/pages/database-administration/standard-databases/migrate-database.adoc
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,28 @@ A migration to a higher `MAJOR` format version or another format is a manual act
13
13
14
14
The store format for new databases can be set with the xref:configuration/configuration-settings.adoc#config_db.format[`db.format`] configuration setting.
15
15
16
+
The table below shows supported migration paths between different Neo4j store formats.
17
+
However, the `standard` and `high_limit` store formats are deprecated starting with Neo4j 5.23, meaning that migration to these formats is not recommended from this version onward.
|`block` footnote:1[The `block` format is the default in Enterprise Edition starting from Neo4j 5.22.] | |{check-mark} Not recommended |{check-mark} Not recommended |
27
+
28
+
|`aligned` footnote:2[The `aligned` format is the default in Community Edition. In Enterprise Edition, it was default before Neo4j 5.22.] ^|{check-mark} | |{check-mark} Not recommended |
29
+
30
+
|`high_limit` footnote:3[label:enterprise[Enterprise Edition] The `high_limit` format is deprecated in 5.23.] ^|{check-mark} | | |
31
+
32
+
|`standard` footnote:4[label:community[Community Edition] The `standard` format is deprecated in 5.23.] ^|{check-mark} ^|{check-mark} |{check-mark} Not recommended |
33
+
|===
34
+
35
+
Before migrating from `block` to the `aligned` format, you have to ensure that your graph fits in the `aligned` since the `block` format has higher limits.
36
+
For details, see xref:database-internals/store-formats.adoc#store-formats-entity-limits[Database internals and transactional behavior -> Store formats].
37
+
16
38
== Syntax
17
39
18
40
The `neo4j-admin database migrate` has the following syntax:
Copy file name to clipboardExpand all lines: modules/ROOT/pages/database-internals/store-formats.adoc
+20-8Lines changed: 20 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ Neo4j's storage engine supports several store formats that describe how data is
6
6
`block` format is the recommended format for Enterprise Edition due to its superior performance and scalability.
7
7
`block` format uses advanced data structures and inlining techniques to enhance data locality, which leads to better resource utilization.
8
8
9
-
`aligned` is the recommended format for Community Edition.
9
+
`aligned` is the default format for Community Edition.
10
10
11
11
`standard` and `high_limit` formats are deprecated in Neo4j 5.23.
12
12
It is not recommended to use these formats for new databases.
@@ -33,6 +33,9 @@ Supports the highest limits at the time of writing.
33
33
See <<block-format-limits, Block format entity limits>> for details. +
34
34
Supports token names (including label, property key, and relationship type names) of any length up to the GQL identifier max length of 16,383 characters.
35
35
* *Future-proofing:* Designed to be extended and improved without requiring store migrations. New features such as data types, or performance enhancements are available without rewriting the store.
36
+
* *Supported migration paths to other store formats:* Although it is not recommended, you can change your store format from `block` to `aligned` or `high_limit`.
37
+
Note that `high_limit` is deprecated.
38
+
The `aligned` format has lower limits than `block`, so your graph must fit within those reduced limits.
36
39
37
40
Aligned::
38
41
* Default format in Community Edition and for all new databases in Enterprise Edition prior to Neo4j 5.22.
@@ -41,13 +44,8 @@ Aligned::
41
44
* *Property access:* Stores graph data in linked list-like structures on disk.
42
45
* *Entity limits:* Supports graphs within some limits.
43
46
See <<aligned-limits, Aligned format entity limits>> for details.
44
-
45
-
Standard:: label:deprecated[Deprecated in 5.23]
46
-
* *Performance:* Basic, foundational format.
47
-
* *Property access:* Stores graph data in linked list-like structures on disk.
48
-
* *Entity limits:* Supports graphs within some limits.
49
-
See <<standard-limits, Standard format entity limits>> for details.
50
-
* For information on deprecation and eventual removal, see <<format-deprecations, Format deprecations>>.
47
+
* *Supported migration paths to other store formats:* You can change your store format from `aligned` to `block` or `high_limit`.
48
+
Note that the `high_limit` format is deprecated, therefore, it is not recommended to migrate to it.
51
49
52
50
High_limit:: label:enterprise-edition[] label:deprecated[Deprecated in 5.23]
53
51
* *Performance:* Performs slightly worse than `standard` and requires more disk space, but allows more nodes and relationships.
@@ -56,6 +54,17 @@ High_limit:: label:enterprise-edition[] label:deprecated[Deprecated in 5.23]
56
54
* *Entity limits:* From the record formats, supports the highest limits at the time of writing.
57
55
For more information, see <<high-format-limits, High_limit format entity limits>>.
58
56
* For information on deprecation and eventual removal, see <<format-deprecations, Format deprecations>>.
57
+
* *Supported migration paths to other store formats:* You can migrate to the `block` format only.
58
+
59
+
Standard:: label:deprecated[Deprecated in 5.23]
60
+
* *Performance:* Basic, foundational format.
61
+
* *Property access:* Stores graph data in linked list-like structures on disk.
62
+
* *Entity limits:* Supports graphs within some limits.
63
+
See <<standard-limits, Standard format entity limits>> for details.
64
+
* For information on deprecation and eventual removal, see <<format-deprecations, Format deprecations>>.
65
+
* *Supported migration paths to other store formats:* You can change your store format from `standard` to `aligned`, `block`, or `high_limit`.
66
+
However, it is not recommended to migrate to the `high_limit` format as it is deprecated.
67
+
59
68
60
69
[[format-deprecations]]
61
70
== Format deprecations
@@ -81,6 +90,9 @@ The last version of Neo4j to include these formats will be an LTS release planne
81
90
+
82
91
. *How can I change the store format of my database?* +
83
92
For information on changing the store format of an existing database, see <<change-store-format, Changing the store format of existing databases>>.
93
+
+
94
+
. *From which store formats can I migrate, and to which formats?* +
95
+
For information about supported migration paths, refer to xref:tools/neo4j-admin/migrate-database.adoc#supported-migration-paths[Neo4j Admin -> Migrate a database].
0 commit comments