Providing a dump version of Hetionet #43
Comments
|
Ah the Note that the production database is still using Neo4j 3.5 (#32), so that might also create issues. Will need to check whether I won't have time immediately to look into this, so let us know if you're able to create the dump which we could point other users towards. |
|
Thanks for the quick response! I currently use neo4j 4.2 and have been unable to run Hetionet without the dump file. I am trying to avoid having two versions of neo4j running at once, but could certainly try that. I am going to keep trying to find work arounds and will certainly let you know if anything works! |
Ideally we could run the export in the Docker container, so its reproducible and doesn't install an extra version of neo4j on the host system. |
|
I would be interested in a dump version too. I am currently using neo4j 4.1.9 also. |
|
I'm able to create the dump file with the following: docker run \
--name=hetionet-container \
--rm \
--publish=7474:7474 \
--publish=7687:7687 \
--volume=$HOME/neo4j/hetionet-data:/data \
--volume=$HOME/neo4j/hetionet-logs:/logs \
dhimmel/hetionet:hetionet-v1.0_neo4j-3.5.12 \
neo4j-admin dump --to=/data/hetionet-v1.0-neo4j.dumpWill look into whether this dump from neo4j 3.5.12 can be loaded into neo4j 4+. |
dhimmel
added a commit
that referenced
this issue
Jul 10, 2022
|
Okay dump file located at I haven't tested CC @ldnam. Perhaps you can try importing this file via neo4j desktop and see if it works! |
|
Hi, first of all thank you for your work on HetioNet. However, I am stuck. It throws some error (a pretty big log file). |
Can you provide the error message and and note what version of Neo4j Desktop you're using? Put the log in a code block and if it is too large I'll edit your comment to use |
|
Thanks for the blazing fast response. Neo4j Desktop: Neo4j Community version: Expand for Neo4j Desktop LogThis is the main.log of Neo4J Desktop when I try to "Create new DBMS from dump"
I also tried creating a fresh DBMS and then importing the dump without success. I'm trying to share the logs specific to this instance but they appear to be empty due to some permission issue.. Is there any well-known issue I'm unaware of? Is it the version of Neo4j ? Any help would be greatly appreciated. |
|
I think the "Neo4j DBMS logs" is where the actual error message for loading the dump file is. Is this the file you're referring to as unavailable due to:
I'm pretty sure the issue is that the dump was created in neo4j 3.5.12 and the dump files are not compatible across major releases. Ideally, we can create a dump for Neo4j 4, but no timeframe on that. |
|
Yes indeed, that's the file I haven't been able to check yet.
Yeah, I had similar thoughts/worries. Perhaps, one way out of converting hetionet once again for later versions of Neo4j would be to use the docker image (?) If I end up doing the conversion for later versions like |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi! Would it be possible to get a .dump version of Hetionet? I use multiple databases in neo4j and have found that this is easiest for loading new databases. By dump version, I mean one created via the neo4j-admin dump command which has file extension .dump (I can give more details if necessary)
Thanks!
The text was updated successfully, but these errors were encountered: