[
https://issues.apache.org/jira/browse/TINKERPOP3-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dylan Millikin updated TINKERPOP3-1005:
---------------------------------------
Description:
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 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.
was:
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 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.
> gremlin-server should throw a 500 error on commit() failure
> -----------------------------------------------------------
>
> Key: TINKERPOP3-1005
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-1005
> Project: TinkerPop 3
> 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 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.3.4#6332)
