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

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

We could create a Step interface called {{RequiresStrategy}}. Its a special 
interface that when the traversal is submitted, the steps are scanned for 
required strategies and then they are added. The problem, a resort of the 
strategies on each traversal creation off of traversal source.

> Consider Required TraversalStrategies
> -------------------------------------
>
>                 Key: TINKERPOP3-669
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-669
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: process
>            Reporter: stephen mallette
>            Priority: Minor
>
> As we now execute the Gremln process suite with and without strategies 
> applied, it became apparent that some strategies are simply "required".  See:
> https://github.com/apache/incubator-tinkerpop/blob/0d239c05638269e6cd5c7af7bd3c61a50627d0bc/tinkergraph-gremlin/src/test/java/org/apache/tinkerpop/gremlin/tinkergraph/process/TinkerGraphNoStrategyComputerProvider.java#L41-L46
> https://github.com/apache/incubator-tinkerpop/blob/0d239c05638269e6cd5c7af7bd3c61a50627d0bc/tinkergraph-gremlin/src/test/java/org/apache/tinkerpop/gremlin/tinkergraph/process/TinkerGraphNoStrategyProvider.java#L42
> Not sure what this means in the grand scheme of things. A few things that 
> feel weird or require more thought:
> 1. Kinda weird that a {{Traversal}} requires any strategies at all to execute.
> 2. Kinda weird that a {{Step}} should know anything about strategies as is 
> the case with {{ConjunctionStrategy}} for example.
> 3. If required strategies are expected then should those required strategies 
> be somewhere more prominently maintained/documented/etc than just being 
> relegated to the test suite
> Not sure anything really needs to change here, just wanted to create an issue 
> for future thought.



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

Reply via email to