apoc.refactor.cloneNodes() not compatible with (existence + unique) or node key constraints

[InverseFalcon]

Expected Behavior (Mandatory)

Execution of apoc.refactor.cloneNodes() (and other clone operations) should be able to succeed even when existence and node key constraints are on the nodes in question, provided that the outcome of the refactoring should not violate the constraints

Actual Behavior (Mandatory)

The refactoring fails, producing an error indicating a constraint violation. This appears to be because the refactoring first creates empty nodes with the given labels and then later populates their properties, tripping on the existence requirements of the constraints.

Note that when ONLY an existence constraint is present the refactoring will succeed, but if either existence + unique constraints are present on the same properties, or a NODE KEY constraint is present, the attempt will fail.

We may need to reorder the operations such that the labels are applied after properties are set, instead of before.

How to Reproduce the Problem

Steps (Mandatory)

1. Use :play movies from the browser to create the sample graph in an empty db.
2. Execute CREATE CONSTRAINT ON (p:Movie) ASSERT (p.title, p.released) IS NODE KEY
3. Execute the following:

MATCH (m:Movie) 
WITH m 
LIMIT 5
CALL apoc.refactor.cloneNodes([m], true) YIELD input, output 
RETURN output

The error will occur.

Alternately, create both a unique constraint and an existence constraint on the same property and attempt the clone operation, the same kind of error should occur

Specifications (Mandatory)

Currently used versions:

Versions

• Neo4j: 4.3.10, 4.4.4
• Neo4j-Apoc: 4.3.x.x, 4.4.0.3