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 2015/09/10 17:16:45 UTC
[jira] [Assigned] (TINKERPOP3-789) Choose then Enforce Semantics
for Graph.close()
[ https://issues.apache.org/jira/browse/TINKERPOP3-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stephen mallette reassigned TINKERPOP3-789:
-------------------------------------------
Assignee: stephen mallette (was: Marko A. Rodriguez)
> Choose then Enforce Semantics for Graph.close()
> -----------------------------------------------
>
> Key: TINKERPOP3-789
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-789
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: structure, test-suite
> Affects Versions: 3.0.1-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
> Fix For: 3.1.0-incubating
>
>
> 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)