You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Florian G (Jira)" <ji...@apache.org> on 2022/03/14 14:41:00 UTC
[jira] [Created] (TINKERPOP-2719) hasNext is called on TraverserIterator after transaction is committed
Florian G created TINKERPOP-2719:
------------------------------------
Summary: hasNext is called on TraverserIterator after transaction is committed
Key: TINKERPOP-2719
URL: https://issues.apache.org/jira/browse/TINKERPOP-2719
Project: TinkerPop
Issue Type: Bug
Components: server
Affects Versions: 3.5.2
Reporter: Florian G
In {{{}TraversalOpProcessor{}}}, the {{hasNext()}} [function is called|https://github.com/apache/tinkerpop/blob/a52887d084053cd420580a0c0a80e745b49ee252/gremlin-server/src/main/java/org/apache/tinkerpop/gremlin/server/op/traversal/TraversalOpProcessor.java#L428] on a {{TraversalIterator}} object after the transaction [is committed|https://github.com/apache/tinkerpop/blob/a52887d084053cd420580a0c0a80e745b49ee252/gremlin-server/src/main/java/org/apache/tinkerpop/gremlin/server/op/traversal/TraversalOpProcessor.java#L414]. This causes issues if the database tries to further execute the traversal upon the {{hasNext()}} call but has no access to the transaction anymore.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)