[
https://issues.apache.org/jira/browse/TINKERPOP-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Mallette closed TINKERPOP-3238.
---------------------------------------
Fix Version/s: 4.0.0
3.7.7
3.8.2
Assignee: Stephen Mallette
Resolution: Done
> 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
> Assignee: Stephen Mallette
> Priority: Major
> Fix For: 4.0.0, 3.7.7, 3.8.2
>
>
> {{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)
