[TINKERPOP-1035] Better Consistency in Gremlin Server Transaction Management

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Implemented
• Affects Version/s: 3.1.0-incubating
• Fix Version/s: 3.1.1-incubating
• Component/s: server
• Assignee: Stephen Mallette
• Reporter: Stephen Mallette
• Created: 08/Dec/15 22:20
• Updated: 19/May/16 16:58
• Resolved: 12/Jan/16 15:16

Description

For sessionless requests to gremlin server, transactions management needs to be tightened such that serialization occurs in the same thread of execution as iteration. This should ensure proper operation across different graphs providers (as some are more strict that others when it comes to transactions). It will also ensure that "extra" transactions are not required to gather data for serialization purposes which should make requests more efficient. Also, transaction management needs to better ensure that the commit of a successful request is complete before the client receives the final streamed message (seems like it was possible for a race condition there)

Issue Links

• links to: GitHub Pull Request #316