[
https://issues.apache.org/jira/browse/TINKERPOP-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko A. Rodriguez closed TINKERPOP-1061.
-----------------------------------------
Resolution: Won't Fix
This is not a good idea for various reasons.
1. {{GraphTraversal}} is bound to context and as such, if {{TinkerGraph}}
implemented it, it would only support a single query at a time.
2. TinkerGraph is the reference implementation of TinkerPop and this is NOT how
developers should be implementing their graph system.
3. There is more to a graph traversal than just {{GraphTraversal}}. Registered
strategies, bulks, sideEffects, sacks, etc. The complications of getting this
involved in TinkerGraph is too much.
4. Gremlin Server registers traversal sources and if TinkerGraph was both
{{Graph}} and a {{GraphTraversal}}, where is the traversal source coming from?
Likewise, how would Gremlin Server behave with such overloading and thread
safety issues.
Please feel free to reopen if there is a design that is elegant and makes
sense, but from how I see it, this would be a radical change that would effect
too many things (and in an awkward error prone way).
> Default Traversal on TinkerGraph
> --------------------------------
>
> Key: TINKERPOP-1061
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1061
> Project: TinkerPop
> Issue Type: Improvement
> Components: process, structure
> Affects Versions: 3.1.0-incubating
> Reporter: Matthias Broecheler
>
> In the vast majority of cases, users will be exploring a TinkerGraph through
> the default traversal that is created via {{graph.traversal()}} and as such
> it would be a nice improvement to have TinkerGraph implement
> {{GraphTraversal}} which is simply a proxy to {{graph.traversal()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
