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

Update Neo4j to 5.x #819

Merged
merged 3 commits into from
Apr 16, 2024
Merged

Update Neo4j to 5.x #819

merged 3 commits into from
Apr 16, 2024

Conversation

jtronge
Copy link
Collaborator

@jtronge jtronge commented Apr 11, 2024

This should update BEE to use neo4j 5.x. See issue #817. I've updated the Python API and made a couple changes to how neo4j is launched.

This is still a WIP but I'm opening it now to see if the CI passes.

This updates the neo4j container management code and driver version.
The gdb code has also been updated to work with the new driver version,
which made breaking changes to how transaction functions are handled.

No changes have been made to the cypher queries yet, although they
seemed to work for the cat-grep-tar workflow.
@pagrubel
Copy link
Collaborator

@jtronge Is this still WIP? Maybe we need to revisit our labels.

@jtronge
Copy link
Collaborator Author

jtronge commented Apr 16, 2024

I think this might be ready for more local testing now.

Maybe we should change WIP so that it always runs CI actions? That's the only reason I left it off, so that I could run this PR through CI. I think we set it that way in the first place to avoid wasting CI time, but I'm not sure that's still a major problem.

Copy link
Collaborator

@pagrubel pagrubel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good. I made minor changes to documentation and the feature to pull the container.

@pagrubel pagrubel merged commit e90da17 into develop Apr 16, 2024
5 checks passed
@pagrubel pagrubel deleted the neo4j-update branch April 16, 2024 22:32
@pagrubel pagrubel mentioned this pull request May 13, 2024
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 this pull request may close these issues.

2 participants