[ https://issues.apache.org/jira/browse/TINKERPOP-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15504440#comment-15504440 ]
David M. Brown commented on TINKERPOP-1453: ------------------------------------------- We haven't looked at async functionality yet at all for the gremlin-python remote connection. In goblin we queue responses on queues that are mapped to request ids: https://github.com/ZEROFAIL/goblin/blob/new_gremlin_python/goblin/driver/connection.py#L268 > Allow Gremlin-Python to handle asynchronous failure > --------------------------------------------------- > > Key: TINKERPOP-1453 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1453 > Project: TinkerPop > Issue Type: Improvement > Components: driver, language-variant > Affects Versions: 3.2.2 > Environment: Titan 1.1 > Gremlin 3.2.2 > Reporter: Carlos Cheung > > Titan occasionally returns transaction errors for a transaction that was sent > a few requests back. Since Gremlin-Python assumes a request sent will get > only its own answer back, this can cause the request-answer to no longer be > in sync and there is no mechanism to recover. > It would be nice to have a way for the receiver to check the request-id to > see if it corresponds to the original request. Additionally there should be a > rolling transaction log in the case of a server error, so a recovery/try > might be possible. > By implementing this, it would be possible to send Gremlin queries > asynchronously as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)