Closed ghost closed 8 years ago
Also, the returned err is null.
Thanks for spotting this. Which graph database (and version) are you using?
I'm using Titan 1.0. DockerFile repo here: https://github.com/realolliebee/db
Do you get any warnings/errors in the gremlin server terminal by chance? (I didn't have time to try your Dockerfile yet, sorry).
Otherwise, I'm guessing an issue with the type of id
where Titan expects a long and gremlin server interprets that id
as an integer.
edit: typo
No errors in the gremlin server terminal. Do you know if there's some advanced error reporting I can enable?
You can try starting gremlin-server with the -v
(verbose) flag.
The verbose flag didn't help, but I figured it out anyway. It only fails for 'id' and 'ID' (though not for 'Id' or 'iD'). I'm guessing 'id' is reserved, similar to 'label'. I'll close the issue, but you should probably update your bound parameters example (and maybe make a note about id): https://github.com/jbmusso/gremlin-javascript#adding-bound-parameters-to-your-scripts
Thanks for the help!
There are a few new reserved keys in titan 1.0 . key
is another one.
Thanks @PommeVerte, do you know if that's documented anywhere?
Not that I could find. I also asked about a full list but haven't heard back yet. I would assume the following are reserved:
key
id
label
value
(not sure)
// Doesn't work client.execute("g.V(id).valueMap()", {id:53408}, function(err, results) { console.log(results); next(); });
// Works client.execute("g.V(53408).valueMap()", function(err, results) { console.log(results); next(); });