You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2015/10/08 13:38:26 UTC

[jira] [Closed] (TINKERPOP3-869) Adding a UtilityOpProcessor for gremlin-server

     [ https://issues.apache.org/jira/browse/TINKERPOP3-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette closed TINKERPOP3-869.
---------------------------------------
    Resolution: Won't Fix

> Adding a UtilityOpProcessor for gremlin-server
> ----------------------------------------------
>
>                 Key: TINKERPOP3-869
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-869
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.0.1-incubating
>            Reporter: Dylan Millikin
>            Assignee: stephen mallette
>            Priority: Minor
>
> This is a proposal for the addition of a UtilityOpProcessor.
> The initial idea behind this OpProcessor is to allow driver developers to have easier means of testing their error management. But it could extend beyond that.
> The initial implementation would probably possess an op of {{throw}} that would be fed the following {{args}}:
> {code}
> { 
>    "exception": {"message":"This is an error.", "code":500}
> }
> {code}
> Or we could also imagine :
> {code}
> { 
>    "exception": {"class":"OpProcessorException", "message":"This is an error.", "code":500}
> }
> {code}
> Though I'm not sure how useful this would be. And it would probably also have security implications so it's really just here for posterity.
> ---
> After receiving these the server would return the described error as per the driver building documentation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)