[
https://issues.apache.org/jira/browse/TINKERPOP3-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710195#comment-14710195
]
Marko A. Rodriguez commented on TINKERPOP3-620:
-----------------------------------------------
Note {{FilterRankStrategy}}. Its very related to this idea in that it resorts a
chain of filters favoring those that are cheaper to execute.
https://github.com/apache/incubator-tinkerpop/blob/master/gremlin-core/src/main/java/org/apache/tinkerpop/gremlin/process/traversal/strategy/optimization/FilterRankingStrategy.java
> Commutative Step Marker interface
> ---------------------------------
>
> Key: TINKERPOP3-620
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-620
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.0.0-incubating
> Reporter: Matthias Broecheler
>
> Some steps can be reordered, i.e. they are commutative. For instance,
> has-steps can be reordered without affecting the pipeline. When writing a
> query optimizer I am often in a situation where I can only optimize a subset
> of the supported steps and I might want to reorder them so that I can group
> all the optimizable steps together. Currently, I have to manually identify
> the commutative steps for that. It would be much nicer if TinkerPop could
> have a "Commutative" marker interface for that and use it consistently.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
