-
Notifications
You must be signed in to change notification settings - Fork 29
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
neo4r not working with latest Neo4j Version 4.0 #69
Comments
Same issue. Any thoughts. |
Well, for now you might just stick with the 3.5 version of Neo4J and it works. |
I'd be happy to review a PR that update this |
Just adding my name to the list of people having an issue with this. |
Hey folks, Can you confirm that only the Cheers, |
Not super helpful but - so far - yes. But my testing hasn't been entirely thorough (I'm in the DB creation stages). |
Some weeks ago it didnt work. Hope it helps! Never said, thank you a lot for this nice package! Helps a lot! |
Thanks @MarianTie I suspect there has been some changes in the REST api endpoint names, and the fact that some methods don't work anymore seem to confirm that, and confirms that it's not the connection itself which is broken, thanks for checking. I'll should have some time to check on this by the end of this month. (But if anybody wants to tackle that in the meantime, I would be happy to help pointing to where to look and review a PR) Colin |
Seems like the endpoints powering these methods have been removed : |
Dear All, |
When trying to ping the latest neo4j database version 4.0, i receive this message:
With the previous version 3.5.14 everything works fine.
It would be nice to update neo4r so that the connetion is also possible with the newest neo4j version.
The text was updated successfully, but these errors were encountered: