Document update/change/delete in block format incremental import

[renetapopova]

No description provided.

[neo-technology-commit-status-publisher]

This PR includes documentation updates
View the updated docs at https://neo4j-docs-operations-2177.surge.sh

Updated pages:

• Import

[tinwelint]

Leaving the property identifier empty is like having a “*” wild card.

I don't understand what this refers to, or why it's mentioned with UPDATE.

[renetapopova]

This I saw it in the PRD where I was looking for information. This was the example:

:START_ID,:END_ID,:TYPE,prop1:int{identifier=true},prop2:string{identifier=true},prop3,:ACTION
0        ,1      ,R    ,0                         ,Hi                           ,Bob  ,UPDATE
0        ,1      ,R    ,1                         ,                             ,Joe  ,UPDATE

Leaving the identifier property empty is like having a “*” wild card.

[tinwelint]

I think that should be a specific note for relationship updates/deletes and the more correct terminology would probably be an "identifier property", of which there can be zero, one or many.

[tinwelint]

This should be covered elsewhere, but the semicolon for array delimiter is the default and can be configured using a command option. So either this note should mention that information too, or just don't include this information at all?

[renetapopova]

I couldn't find it anywhere on this page.

[renetapopova]

And I also didn't know that the semicolon for array delimiter is the default. Why do we need to mention that it can be configured using a command option given that it's already configured to be the default?

[tinwelint]

Because if the manual mentions that it's a semicolon that is the delimiter then it looks like that's that, right. Better to perhaps talk about "array delimiter character (which defaults to semicolon)" to be clear on that!

[tinwelint]

I think it's starting to look much better!

Had a comment about -PROPERTY, which is still not quite what it should be

[tinwelint]

This isn't how it works either. To remove properties you add this :-PROPERTY column and for each entity, the values in this column specifies which properties to remove. E.g:

:ID,:-PROPERTY,somePropToSet,someOtherPropToSet
1,unwantedProp1,"Hello","There"
2,unwantedProp1;unwantedProp2,"Hi","Good bye"

Note that somePropToSet and someOtherPropToSet or completely normal property columns, unrelated to :-PROPERTY.

[renetapopova]

Ok, so in this case:

:ID,:LABEL,:-PROPERTY,age,hometown
person1,Actor,55,New York

it will remove some property (which I don't know what it is), and will leave the rest.
Is that the case?
Also in your example, there is no label but further up, you said that nodes are identified by their unique property value for the key/label combination that the header specifies. Doesn't this mean that the header should contain a label as well?

[tinwelint]

Your example should be:

:ACTION,:ID,:-PROPERTY
U,person1,age;hometown

and then a more meaningful example would probably state the full capabilities of update, i.e. to add/remove labels and set/remove properties all at the same time (I'm not good at examples):

:ACTION,uid:ID(label:Person),:LABEL,:-LABEL,:-PROPERTY,name,height:int
U,person1,Actor,Producer,age;hometown,"Henry",185

(And also the usual way of identifying nodes in incremental still apply, i.e. you need to specify e.g. uid and Person to let it know which uniqueness constraint you're looking up the nodes in.

See, one CSV entry can specify all types of updates to one entity at the same time. Here the node person1 is updated with:

• added Actor label
• removed Producer label
• removed age and hometown properties
• set name="Henry" property
• set height=185 property

[tinwelint]

Suggestion: "You can remove properties from existing nodes or relationships by adding a :-PROPERTY column in the header. In the contents of this field you can add zero or more property names to remove from the entity".

[tinwelint]

Your example should be:

:ACTION,:ID,:-PROPERTY
U,person1,age;hometown

and then a more meaningful example would probably state the full capabilities of update, i.e. to add/remove labels and set/remove properties all at the same time (I'm not good at examples):

:ACTION,uid:ID(label:Person),:LABEL,:-LABEL,:-PROPERTY,name,height:int
U,person1,Actor,Producer,age;hometown,"Henry",185

(And also the usual way of identifying nodes in incremental still apply, i.e. you need to specify e.g. uid and Person to let it know which uniqueness constraint you're looking up the nodes in.

See, one CSV entry can specify all types of updates to one entity at the same time. Here the node person1 is updated with:

• added Actor label
• removed Producer label
• removed age and hometown properties
• set name="Henry" property
• set height=185 property

[tinwelint]

This example has the same problem as above

[recrwplay]

This PR includes documentation updates
View the updated docs at https://neo4j-docs-operations-2177.surge.sh

Updated pages:

• Import

[tinwelint]

I don't know how we do elsewhere, but technically the "correct" line would include all the other column separators too e.g. DELETE,person4,, but it's not strictly necessary. I'd guess the example looks better without them 🤷

[tinwelint]

"acts" -> "helps" ?

[tinwelint]

There can be multiple identifier properties defined in the header. Perhaps you already mention this implicitly in this sentence, your call.

[tinwelint]

This row is missing content in its -LABEL column. It has

• uid:ID{label:Person} = person1
• :+LABEL = Actor;Director (i.e. add both these labels)
• :-LABEL = Laurence Fishburne (i.e. remove label Laurence Fishburne)
• name = 60
• age = <empty>

[tinwelint]

Is it intentional to state this fact here too, about how nodes/relationships are identified?

[tinwelint]

The contents of the field which in this example is 55;New York should be property names, not property values e.g. instead age;hometown

[tinwelint]

Likewise here: Neo;"The chosen one" are property values. The contents of this field should be property names, e.g. name;role or something like that.

[tinwelint]

Same problem with :-PROPERTY here, i.e. 45;New York should instead be age;hometown