Head's Up! These forums are read-only. All users and content have migrated. Please join us at community.neo4j.com.
07-13-2020 09:19 AM
We recently ( Saturday night) upgrade the Neo4j DB servers to 4.1. At the same time we upgraded all of the desktops. So we are all on 4.1 across the board. Latest releases.
As soon as we did, three things went wrong. One is annoying (1) but 2 & 3 are almost fatal.
When we access it from the desktop app, and connect using that environment, it all works perfectly. But as it stands, we are crippled and of course, installing neo4j desktop on all the users desks is unacceptable.
I don't see anyone else complaining. Need help though.
07-15-2020 03:36 AM
Hi Bill, APOC releases are updated frequently these days...
There is a "Core" and a "Full" version now.
Double-check on https://github.com/neo4j-contrib/neo4j-apoc-procedures/releases/ that you are using the one matching the 4.1 release.
Make sure there is only one in the plugin folder; I would try them both and see if they have different behaviour.
On that transaction set could you tell us a bit more on what kind of data it is and how you load it? Presumably with APOC calls but which ones?
Regarding #3 ; are you referering to connecting to the graph via the webinterface running on the server? The http://server.ip:7474/ one? Make sure you cleared your cookies and cache after the upgrade.
Hope this helps..
All the sessions of the conference are now available online