[
https://issues.apache.org/jira/browse/TINKERPOP-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP-634.
--------------------------------------
Resolution: Won't Fix
Assignee: stephen mallette
I don't think this is a useful idea anymore. {{TraversalSource}} provides
access to the {{Graph}} instance that instantiated it, so not super useful to
"hide" a {{Graph}} because it can be accessed anyway. I think a workaround
exists, in that you could use an init script to construct a new {{Graph}} and a
{{TraversalSource}} but only return the {{TraversalSource}} in the global
bindings. That would serve the same purpose as "hiding".
> Configurable Graph Hiding in Gremlin Server
> -------------------------------------------
>
> Key: TINKERPOP-634
> URL: https://issues.apache.org/jira/browse/TINKERPOP-634
> Project: TinkerPop
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.0.2-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
>
> A user may want to configure a {{Graph}} to only be bound to the server for
> purpose of creating a {{TraversalSource}} and server-driven transaction
> management. In this way, the user can "secure" their {{Graph}} locking it
> down behind the {{TraversalSource}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
