[jira] [Commented] (TINKERPOP-2078) Hide use of EmptyGraph or RemoteGraph behind a more unified method for TraversalSource construction

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

    [ https://issues.apache.org/jira/browse/TINKERPOP-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662879#comment-16662879 ] 

stephen mallette commented on TINKERPOP-2078:
---------------------------------------------

Perhaps one final thought for the day - go with this approach, which seems really easy to explain:

* Have a local {{Graph}} instance? then do {{g = graph.traversal()}}
* Don't have a local {{Graph}} instance because you're remoting? then do {{g = traversal().withRemote(...)}}

this way we rely on the existing {{TraversalSource}} builder methods that are still hanging about and we hide {{EmptyGraph}} and {{RemoteGraph}} from folks. If we like the approach shown in the previous comment then we can easily add those helper methods at a future point. At this point I think i'm inclined to go this route.

> Hide use of EmptyGraph or RemoteGraph behind a more unified method for TraversalSource construction
> ---------------------------------------------------------------------------------------------------
>
>                 Key: TINKERPOP-2078
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2078
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: structure
>    Affects Versions: 3.3.4
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>            Priority: Major
>
> {{RemoteGraph}} was long ago deprecated for {{withRemote()}} typically spawned from {{EmptyGraph}} which is weird. For GLVs, make sure {{EmptyGraph}} didn't leak into them and deal with those issues as needed. Update all docs to stop using {{EmptyGraph}}. Provide a way to unify {{TraversalSource}} construction for both local and remote connected graphs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)