[jira] [Updated] (TINKERPOP-789) Choose then Enforce Semantics for Graph.close()

["stephen mallette (JIRA)" <ji...@apache.org>]

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

stephen mallette updated TINKERPOP-789:
---------------------------------------
    Fix Version/s:     (was: 3.2.3)

Seems we are a bit deep into 3.2.x to implement this now - removing the fix version - perhaps we look for 3.3.0

> Choose then Enforce Semantics for Graph.close()
> -----------------------------------------------
>
>                 Key: TINKERPOP-789
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-789
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: structure, test-suite
>    Affects Versions: 3.0.2-incubating
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>
> The semantics for {{Graph.close()}} are fairly open  right now.  See TinkerGraph:
> {code}
> gremlin> graph = TinkerFactory.createModern()
> ==>tinkergraph[vertices:6 edges:6]
> gremlin> graph.close()
> ==>null
> gremlin> graph.vertices()
> ==>v[1]
> ==>v[2]
> ==>v[3]
> ==>v[4]
> ==>v[5]
> ==>v[6]
> {code}
> Seems like a call to {{close()}} should mean something especially since we implement {{AutoCloseable}}.  I believe that most graphs throw exceptions (Titan does {{IllegalStateException}} i think) if you try to access the graph once {{close()}} is called.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)