-
Notifications
You must be signed in to change notification settings - Fork 62
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
client.execute not working with Tinkerpop Server 3.2.3… #61
Comments
I'm having the same issue. |
This is related to the connection URL string which now requires to append On Friday, 28 October 2016, Victor O. Santos Uceta [email protected]
Jean-Baptiste |
Thanks Jean! By the way, we are integrating your driver to our new database, it will be working soon 👍 Give it a look here: TruenoDB |
Indeed, adding this to the beginning of the GremlinClient constructor seems to fix the connection issue:
(it would probably be worth looking into ways to timeout and give some feedbacks, in cases like this where the path is not correct) |
Actually, it's not documented but you can supply a |
When running either example code or
npm run examples:node
, the script seems to start fine and even connect to the socket (throws an error if the server is not running), butclient.execute
's callback never gets called.Tinkerpop Server version is: 3.2.3 and started with:
./bin/gremlin-server.sh conf/gremlin-server-classic.yaml
Node version is: 7.0 (but also tried with v6.9.1: same results).
npm version is: 3.10.8
Connecting to the Tinkerpop Server with gremlin console or through the Python interface works fine.
The text was updated successfully, but these errors were encountered: