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

client.execute not working with Tinkerpop Server 3.2.3… #61

Open
zedrdave opened this issue Oct 28, 2016 · 5 comments
Open

client.execute not working with Tinkerpop Server 3.2.3… #61

zedrdave opened this issue Oct 28, 2016 · 5 comments

Comments

@zedrdave
Copy link

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), but client.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.

@vsantosu
Copy link

I'm having the same issue.

@jbmusso
Copy link
Owner

jbmusso commented Oct 28, 2016

This is related to the connection URL string which now requires to append
/gremlin. I need to fix this, hopefully today.

On Friday, 28 October 2016, Victor O. Santos Uceta [email protected]
wrote:

I'm having the same issue.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#61 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMa1Pv5YNhGhgjekN-YJOWF4vfb3UYCks5q4aW5gaJpZM4KjCZr
.

Jean-Baptiste

@vsantosu
Copy link

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

@zedrdave
Copy link
Author

zedrdave commented Oct 29, 2016

Indeed, adding this to the beginning of the GremlinClient constructor seems to fix the connection issue:

const { path = '/gremlin' } = options;

(it would probably be worth looking into ways to timeout and give some feedbacks, in cases like this where the path is not correct)

@jbmusso
Copy link
Owner

jbmusso commented Nov 13, 2016

Actually, it's not documented but you can supply a path option to the option object when instantiating a client. { path: '/gremlin' } should work.

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

No branches or pull requests

3 participants