Looks like we already have an open issue on this topic:
https://issues.apache.org/jira/browse/TINKERPOP-1005
So - good - not closing one issue to just open another :)
On Mon, Sep 19, 2016 at 9:25 AM, Stephen Mallette
wrote:
> Ah - yes - the "locking" issue as specific to Titan. More generally,
Ah - yes - the "locking" issue as specific to Titan. More generally, I am
sure there are other graphs that have retry-able errors that would get
consumed by Gremlin Server. I wonder how that would work though. There
would need to be a way for the Graph to tell Gremlin Server what kind of
error code
Yeah. This should be a client side feature.
I think discussing scenarios where retry is useful to clients and bubbling
up proper errors would be the correct solution to this problem. A good
example would be locks, currently clients have no clean way of detecting
locks and retrying appropriately.
