[
https://issues.apache.org/jira/browse/TINKERPOP-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP-1005.
---------------------------------------
Resolution: Won't Do
Recent changes on other tickets related to 3.2.5 (and perhaps even earlier
versions along the 3.2.x line) have improved error messaging considerably. You
now get the server error message, the server stacktrace and the exception
hierarchy (you would see the specific Titan/JanusGraph exception names). If you
used auto-transactions then a commit error would nowadays return as a 500 not a
597. If you called commit within a script, well then that's a 597, but it
should be a 597 in a sense because it failed as a script. Anyway, I think that
tends to satisfy this one. I'm going to close this as a result - please re-open
if I've not addressed something or this needs more discussion.
> gremlin-server should throw a 500 error on commit() failure
> -----------------------------------------------------------
>
> Key: TINKERPOP-1005
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1005
> Project: TinkerPop
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.0.2-incubating
> Reporter: Dylan Millikin
>
> Currently gremlin-server throws a {{597 - SCRIPT EVALUATION ERROR}} on commit
> failures (for concurrency reasons for example). This isn't really the correct
> error to return in those cases. Drivers would expect a {{500 - SERVER ERROR}}
> instead for their retry-failure strategies.
> Of course this could take on another form and somehow allow drivers to
> differentiate commit failures from other exceptions. So in any event this is
> probably going to depend on
> https://issues.apache.org/jira/browse/TINKERPOP3-1004 yet also require a
> change to the server code.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
