-
Notifications
You must be signed in to change notification settings - Fork 2
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
Expose the Bolt port of the embedded graph #65
Comments
Ugh. It would seem that we can't due (again) to a limitation of neo4j-tinkerpop-api-impl. I based my approach on Accessing Neo4j embedded via the Bolt protocol. In order to get the code to compile, the commented dependencies below were required. implementation "org.apache.tinkerpop:neo4j-gremlin:${gremlinVersion}"
implementation "org.neo4j:neo4j-tinkerpop-api-impl:${neo4jTinkerpopVersion}"
implementation "org.neo4j.driver:neo4j-java-driver:${neo4JavaDriverVersion}"
//implementation "org.neo4j:parent:${neo4JavaDriverVersion}"
//implementation "org.neo4j:neo4j-community:${neo4JavaDriverVersion}"
//implementation "org.neo4j:neo4j-bolt:${neo4JavaDriverVersion}" However, adding the neo4j-bolt dependency causes the following error in our core code:
Our current dependency versions are: groovyVersion=3.0.7
gremlinVersion=3.4.10
neo4jTinkerpopVersion=0.9-3.4.0
neo4JavaDriverVersion=4.1.1
javaVersion=11 Version 0.9-3.4.0 of neo4j-tinkerpop-api-impl was published in January of 2019. Version 4.1.1 of neo4j-java-driver and neo4j-bolt were published in 2020. neo4j-java-driver seems to be ok, but simply adding the dependency neo4j-bolt causes our code to fail even if there is no reference in our code to anything neo4j-bolt. Just adding the dependency messes things up. |
I was able to get it to compile by setting 2.0.0-alpha3 also works. 4.0.0 does not. There doesn't appear to be a 3.x release. https://mvnrepository.com/artifact/org.neo4j.driver/neo4j-java-driver |
Export the Bolt port by default of the embedded graph so that things like Neo4j Desktop can interact with it.
The text was updated successfully, but these errors were encountered: