[ 
https://issues.apache.org/jira/browse/TINKERPOP-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stephen mallette closed TINKERPOP-2261.
---------------------------------------
    Resolution: Won't Do

As mentioned earlier, this item would need some discussion on dev if it were to 
go forward. If the idea is to improve transactional testing in Gremlin Server 
then we'd probably want a different issue specifically for Gremlin Server to 
alter the test framework to make more use of Neo4j (hopefully in a strategic 
way that doesn't greatly expand the already lengthy test cycle). Closing this 
one for now.

> Adding transactions to Tinkergraph for better testability
> ---------------------------------------------------------
>
>                 Key: TINKERPOP-2261
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2261
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: tinkergraph
>    Affects Versions: 3.3.7, 3.4.2
>            Reporter: Divij Vaidya
>            Priority: Major
>
> Tinkergraph should act as a datastore which supports transactions. This would 
> help define tx semantics for Gremlin and add test suites that fail when those 
> semantics are violated. 
> As an example, 
> [https://issues.apache.org/jira/projects/TINKERPOP/issues/TINKERPOP-2257] bug 
> would have been caught by the test suite if the tinkergraph was mimicking 
> transaction support.
> Hence, this task breaks down into:
> 1. Mimic transaction support in TinkerGraph
> 2. Add tests that validate the transaction semantics (e.g. accessing the 
> iterator after the transaction is closed will cause an error)



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to