You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2015/08/27 17:33:45 UTC

[jira] [Commented] (TINKERPOP3-777) TraverserRequirement to be an Interface

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

Marko A. Rodriguez commented on TINKERPOP3-777:
-----------------------------------------------

Can you please provide a more explicit representation of your particular problem?

There are situations in which I would like to have parameters on {{TraverserRequirement}}, but have been able to get away from needing it. Perhaps your use case is the tipping point. ?

> TraverserRequirement to be an Interface
> ---------------------------------------
>
>                 Key: TINKERPOP3-777
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-777
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.0.0-incubating
>            Reporter: pieter martin
>            Assignee: Marko A. Rodriguez
>
> I am trying to optimize {{GraphStep}}.
> {code}
> g.V().hasLabel("Person").out("address")
> {code}
> This will be collapsed into one step.
> However as it is a {{StartStep}} the traverser need to be setup.
> So I created a custom {{TraverserGeneratorFactory}}, {{TraverserGenerator}} and {{Traverser, Traverser.Admin}}.
> However for the {{TraverserGeneratorFactory}} to make its decision it uses the {{TraverserRequirement}} which for now is a enum.
> It needs to be an interface so that I can add a custom requirement to guide the custom {{TraverserGeneratorFactory}} in its decision making.



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