GitHub user spmallette opened a pull request:
https://github.com/apache/incubator-tinkerpop/pull/218
TINKERPOP-1106 Better handled commit and serialization errors in Gremlin
Server.
https://issues.apache.org/jira/browse/TINKERPOP-1106
Both types of errors were causing problems. For commit errors, the last
message from iteration was already sent back to the client as a terminating
message so failure on commit after that was ignored by the driver because it
had already received the terminator for that request. Serialization errors
didn't break the result iteration loop - they were being handled, but the
result iteration was allowed to continue. I'm not so sure that those types of
failures weren't leaking transactions either - that should be fixed now too.
This stuff is hard to write tests for with Gremlin Server as I dont' know
how to force raise a commit exception for Neo4j. I was able to test externally
with graphs that were easier to force that condition.
Tested with: `mvn clean install && mvn verify -pl gremlin-server
-DskipIntegrationTests=false`
VOTE: +1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/incubator-tinkerpop TINKERPOP-1106
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-tinkerpop/pull/218.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #218
----
commit 9f85d3ed73e41313fc5f7981a1899ed0f8482fa6
Author: Stephen Mallette <[email protected]>
Date: 2016-02-03T20:28:25Z
Better handled commit and serialization errors in Gremlin Server.
Both types of errors were causing problems. For commit errors, the last
message from iteration was already sent back to the client as a terminating
message so failure on commit after that was ignored by the driver because it
had already received the terminator for that request. Serialization errors
didn't break the result iteration loop - they were being handled, but the
result iteration was allowed to continue. I'm not so sure that those types of
failures weren't leaking transactions either - that should be fixed now too.
This stuff is hard to write tests for with Gremlin Server as I dont' know
how to force raise a commit exception for Neo4j. I was able to test externally
with graphs that were easier to force that condition.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
