You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Valentyn Kahamlyk (Jira)" <ji...@apache.org> on 2024/01/16 19:28:00 UTC
[jira] [Created] (TINKERPOP-3037) Improve error handling for GraphBinary
Valentyn Kahamlyk created TINKERPOP-3037:
--------------------------------------------
Summary: Improve error handling for GraphBinary
Key: TINKERPOP-3037
URL: https://issues.apache.org/jira/browse/TINKERPOP-3037
Project: TinkerPop
Issue Type: Improvement
Components: server
Affects Versions: 3.7.1, 3.6.6
Reporter: Valentyn Kahamlyk
Now when there is an error with deserializing `RequestMessage` from GLV's, it will hands forever.
The reason is that for any response (including error message) server need a request ID which in this case is lost.
Server can return correct error message when RequestMessage is in correct format, but traversal is invalid, for example:
- newly added steps can't be deserialized, like 3.7.1 client with 3.7.0 server
- some other issues like I got with incorrect type, example for .net GLV: `g.AddV().Property("test", GremlinType.FromFqcn("test")).Next()`
--
This message was sent by Atlassian Jira
(v8.20.10#820010)