[
https://issues.apache.org/jira/browse/TINKERPOP-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP-1030.
---------------------------------------
Resolution: Won't Do
I created this one, but no longer like the idea. Just more complexity in the
gremlin server config that we don't need. No one is really asking for this so
- it's just stuff for the sake of stuff - closing.
> Map common exceptions to HTTP status codes where possible
> ---------------------------------------------------------
>
> Key: TINKERPOP-1030
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1030
> Project: TinkerPop
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.1.0-incubating
> Reporter: stephen mallette
> Priority: Trivial
>
> If a script throws an exception in the REST API, it would be nice if there
> was a way to map that exception to an HTTP status code. The gremlin server
> configuration could have a specific set of exception to error code mappings.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
