-
Notifications
You must be signed in to change notification settings - Fork 4
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
neo4j 4.2.3 installation #9
Comments
I confirm, neo4j 4.x is a biocypher nightmare, most of my dependency hell issues were connected with the fact that you use 4.x version instead of 5.x and also have it in transient dependencies |
Apologies, these issues actually belong to https://github.com/MannLabs/CKG/tree/master which is apparently non maintained. I'll try to come up with a set of scripts and a docker-compose to lower the entry threshold for this, because the prerequisite of "Data |
Yes, this (reproducing the CKG) is a maintenance issue first and foremost. Also one of the reasons we developed the framework in the first place. This CKG version here is a relatively early biocypher pipeline, and as the major lesson, I would not recommend streaming from one Neo4j DB into another if it can be avoided. @antonkulaga I am not sure I get your point. Who/what do you mean with "you"? @winternewt What is the issue with loading the dump? Neo4j 4.x should work fine if you just load the file you can download at the given link. |
I mean that biocypher uses neo4j 4.x, it is also in transient poetry dependencies as well, so switching to 5.x is somewhat a pain. |
Ah, you are referring to the Bolt driver Python package. This issue is about the Neo4j software itself, so only loosely related. We already have plans to remove the dependency on neo4j-utils, as it turned out to be ineffective to separate them. Issue here: biocypher/biocypher#332 @nilskre FYI |
There are numerous environment issues with setting Neo4j 4.x with this dump using the CKG docs, see the issue by mistake opened in this repo for reference: I propose the pull eliminating all those, thus ensuring quick reproducibility, @slobentanzer kindly check |
Reads like a lesson in reproducibility (of which we unfortunately have many) 🥲 Many thanks for opening a PR! Will check it out ASAP |
In https://ckg.readthedocs.io/en/latest/intro/getting-started-with-neo4j.html
For me, on Ubuntu 22:
apt-get install neo4j=1:4.2.3 pulls one of the newer "cypher-shell" packages, which in turn pulls openjdk-17
Solved by specifying exact cypher-shell version matching the neo4j
sudo apt-get install neo4j=1:4.2.3 cypher-shell=1:4.2.3
The text was updated successfully, but these errors were encountered: