-
Notifications
You must be signed in to change notification settings - Fork 493
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
apoc.merge does not return statistics #3652
Comments
Hi! I think you've misunderstood what the fix here did :)
Procedures cannot report to the db statistics, and that is not something that APOC can make a fix for. What that change did, was add new procedures e.g Hope this helps! |
@gem-neo4j Thanks, but that will not work inside apoc.periodic.iterate, is that correct? There is no way to assign the output from the stats column so it shows up in the updateStatistics output for apoc.periodic.iterate, is there? |
Ah I see, yeah there is no way to do that. What I recommend in that case is to use Cypher instead, all the APOC procedure is doing is building a Cypher Query and executing it, so you could run it yourself: e.g for your example:
Is the same as running:
And by running this, you will get the statistics back as expected. I’d also recommend using |
Expected Behavior (Mandatory)
I am expecting this query:
To return a summary that includes statistics. This should be fixed, according to this: #2239
Actual Behavior (Mandatory)
The query returns the following summary:
The stats should either have nodesCreated: 1 or propertiesSet: 1, depending on if the node is created or merged.
How to Reproduce the Problem
Steps (Mandatory)
Specifications (Mandatory)
Currently used versions
Versions
The text was updated successfully, but these errors were encountered: