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
@@ -619,6 +619,17 @@ Incremental import into an existing database.
619
619
620
620
=== Usage and limitations
621
621
622
+
[WARNING]
623
+
====
624
+
The importer works well on standalone servers.
625
+
626
+
In clustering environments with multiple copies of the database, the updated database must be used as a source to reseed the rest of the database copies.
627
+
You can use the procedure xref:procedures.adoc#procedure_dbms_cluster_recreateDatabase[`dbms.cluster.recreateDatabase()`].
628
+
For details, see xref:clustering/databases.adoc#recreate-databases[Recreate databases].
629
+
630
+
Starting the clustered database after an incremental import without reseeding or performing the incremental import on a single server while the database remains online on other clustered members may result in unpredictable consequences, including data inconsistency between cluster members.
631
+
====
632
+
622
633
The incremental import command can be used to add:
623
634
624
635
* New nodes with labels and properties.
@@ -638,12 +649,6 @@ The incremental import command cannot be used to:
638
649
* Update or delete labels in nodes.
639
650
* Delete existing nodes and relationships.
640
651
641
-
[NOTE]
642
-
====
643
-
The importer works well on standalone servers.
644
-
In clustering environments with multiple copies of the database, the updated database must be reseeded.
0 commit comments