[
https://issues.apache.org/jira/browse/TINKERPOP-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15626177#comment-15626177
]
Marko A. Rodriguez commented on TINKERPOP-620:
----------------------------------------------
[~mbroecheler] Is this still a desired feature? Can you provide a "gist" of
where in your code you have to explicitly reason about commutativity? This will
help me to better understand the usage.
> Commutative Step Marker interface
> ---------------------------------
>
> Key: TINKERPOP-620
> URL: https://issues.apache.org/jira/browse/TINKERPOP-620
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.0.2-incubating
> Reporter: Matthias Broecheler
> Fix For: 3.2.4
>
>
> 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)
