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 2019/01/30 18:18:00 UTC

[jira] [Closed] (TINKERPOP-1050) Consider an explicit exception for operational exceptions in the driver

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

stephen mallette closed TINKERPOP-1050.
---------------------------------------
    Resolution: Won't Do

Going to stick with general unchecked exceptions for now rather than muck with the APIs and create breaking changes for folks.

> Consider an explicit exception for operational exceptions in the driver
> -----------------------------------------------------------------------
>
>                 Key: TINKERPOP-1050
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1050
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: driver
>    Affects Versions: 3.0.2-incubating
>            Reporter: stephen mallette
>            Priority: Minor
>
> Exceptions returned from the server return as {{ResponseException}}.  Client side exceptions typically populate as {{RuntimeException}}.  This is easily seen with serialization errors on the client.  Perhaps a specific type of exception should be exposed here for "driver" errors.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)