[
https://issues.apache.org/jira/browse/TINKERPOP-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130990#comment-15130990
]
stephen mallette commented on TINKERPOP-1106:
---------------------------------------------
It looks like it would be quite possible that serialization exceptions would
have allowed additional results to be written back to the client as mentioned
on the mailing list. The loop of iteration wasn't breaking on exception.
> Errors on commit in Gremlin Server don't register as exception on driver
> ------------------------------------------------------------------------
>
> Key: TINKERPOP-1106
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1106
> Project: TinkerPop
> Issue Type: Bug
> Components: server
> Affects Versions: 3.1.1-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
> Priority: Critical
> Fix For: 3.1.2-incubating
>
>
> Because the last message in a result is sent before commit as the terminating
> message, a failure on {{commit()}} will send another message, but the driver
> won't be looking for it and it will not register as an exception on that
> request.
> Seems like the solution would be to save the last message until after commit,
> and if the commit fails, you would send the error back otherwise send the
> last message. In this way the protocol doesn't have to change.
> Also need to determine if exceptions prevent additional iteration of results
> back to the client as discussed here:
> https://groups.google.com/d/msg/gremlin-users/H5IlmZ4Zgyc/ENfScPisCgAJ
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
