[
https://issues.apache.org/jira/browse/TINKERPOP-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18074047#comment-18074047
]
Christopher Smith commented on TINKERPOP-3238:
----------------------------------------------
I think I'm the one behind the ticket here, and I would clarify the request to
at a minimum implement {{Failure}}, which is explicitly guaranteed by the API.
Use of {{FailException}} itself would be a substantial improvement on that,
because some functional/reactive pipeline DSLs don't provide a mechanism for
"handle failure of type {{X does-not-extend Exception}}".
> fail() improvements for remote applications
> --------------------------------------------
>
> Key: TINKERPOP-3238
> URL: https://issues.apache.org/jira/browse/TINKERPOP-3238
> Project: TinkerPop
> Issue Type: Improvement
> Components: documentation, driver
> Affects Versions: 3.7.5
> Reporter: Stephen Mallette
> Priority: Major
>
> {{fail()}} step throws a {{FailException}} in embedded mode - it's documented
> as such. For remote with websockets you get a 595 error code but a
> {{FailException}} will not raise even for Java. For HTTP you get a regular
> old 500 exception with an error message that says the fail triggered. Clarify
> this situation in the documentation and consider an approach that can
> actually raise a {{FailException}} in java for the 595.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
