Skip to content
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

Open
winternewt opened this issue May 23, 2024 · 7 comments · May be fixed by #13
Open

neo4j 4.2.3 installation #9

winternewt opened this issue May 23, 2024 · 7 comments · May be fixed by #13

Comments

@winternewt
Copy link

winternewt commented May 23, 2024

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

@antonkulaga
Copy link

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

@winternewt
Copy link
Author

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
CKG Neo4j database dump (available here)" turn out remarkably hard to reconstruct.

@slobentanzer
Copy link
Collaborator

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.

@antonkulaga
Copy link

I am not sure I get your point. Who/what do you mean with "you"?

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.

@slobentanzer
Copy link
Collaborator

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

@winternewt winternewt linked a pull request Jun 4, 2024 that will close this issue
@winternewt
Copy link
Author

winternewt commented Jun 4, 2024

@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.

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:
#10
The db is named 'graph.db' (it was probably migrated from v3) not matching the v4 default naming (neo4j) etc etc etc. Took me a few hours to sort them all out.

I propose the pull eliminating all those, thus ensuring quick reproducibility, @slobentanzer kindly check
#13

@slobentanzer
Copy link
Collaborator

Reads like a lesson in reproducibility (of which we unfortunately have many) 🥲

Many thanks for opening a PR! Will check it out ASAP

@slobentanzer slobentanzer linked a pull request Jun 4, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants