You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2019/07/10 20:34:00 UTC

[jira] [Updated] (TINKERPOP-2261) Adding transactions to Tinkergraph for better testability

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

stephen mallette updated TINKERPOP-2261:
----------------------------------------
    Issue Type: Improvement  (was: Wish)

it's been discussed many a time, but the general consensus has been that we wanted to keep TinkerGraph simple as a code base so the idea has never carried forward. We have Neo4j in TinkerPop almost exclusively for transaction testing of the framework. If we wanted more coverage for transactions in Gremlin Server we should probably just rig up Neo4j to do that. 

> 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.3#76005)