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/import.adoc
+56-18Lines changed: 56 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1464,22 +1464,24 @@ Now use the previously defined ID spaces when connecting the actors to movies.
1464
1464
== Using multiple node IDs
1465
1465
1466
1466
A node header can contain multiple `ID` columns.
1467
-
The relationship data must then use a matching number of `START_ID` / `END_ID` columns as references to the composite value of those ID columns.
1467
+
1468
+
Starting from 2025.07, the relationship data must then use a matching number of `START_ID` / `END_ID` columns as references to the composite value of those ID columns.
1468
1469
This implies using `string` as `id-type`.
1469
1470
1470
1471
For each `ID` column, you can specify to store its values as different node properties.
1471
1472
However, the composite value cannot be stored as a node property.
1472
1473
1473
-
[NOTE]
1474
+
[IMPORTANT]
1474
1475
====
1475
1476
Incremental import doesn't support the use of multiple node identifiers.
1476
1477
This functionality is only available with a full import.
1477
1478
====
1478
1479
1479
1480
1480
-
.Define multiple IDs as node properties
1481
-
====
1481
+
=== Define multiple IDs as node properties
1482
+
1482
1483
You can define multiple `ID` columns in the node header.
1484
+
1483
1485
For example, you can define a node header with two `ID` columns.
0 commit comments