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/05/06 00:30:00 UTC

[jira] [Closed] (TINKERPOP3-654) out -> outE Traversal Strategy

     [ https://issues.apache.org/jira/browse/TINKERPOP3-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marko A. Rodriguez closed TINKERPOP3-654.
-----------------------------------------
    Resolution: Fixed

[~dkuppitz] did this and pushed to master/

> out -> outE Traversal Strategy
> ------------------------------
>
>                 Key: TINKERPOP3-654
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-654
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: process
>            Reporter: Marko A. Rodriguez
>            Assignee: Daniel Kuppitz
>
> When users do {{out.count}}, it is more efficient to do {{outE.count}}. Likewise, {{properties.count}} is better than {{values.count}}. The former is especially true in OLAP where a whole iteration is saved by using {{outE}} over {{out}}. I suspect there are other situations besides {{count}} where this conversion could be useful.
> Thus, a {{HalfStepTraversalStrategy}} would be good.



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