Query generates arbitrary nodes; termination doesn't roll them back about neo4j-apoc-procedures HOT 2 CLOSED

Hello! Thanks for writing in, this is because the procedure was opening its own transaction and then the MATCH (n) sees those nodes created after that transaction is committed, and creates more and so on. This is strange behaviour for sure, I hade stopped it from doing this (which fixes the other bug you reported as well), and it will be available in 5.18 😊

A workaround for this is to collect to a list instead, something like this:

CREATE (primary:demo {uid: 1}), (secondary:demo {uid: 2})
WITH primary AS _
MATCH (n)
WITH collect(n) as nodes
CALL apoc.refactor.cloneNodes(nodes, false, [])
YIELD input, output AS clone, error
RETURN clone

from neo4j-apoc-procedures.

Awesome, @gem-neo4j, thanks for that

from neo4j-apoc-procedures.