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

["Daniel Kuppitz (JIRA)" <ji...@apache.org>]

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

Daniel Kuppitz commented on TINKERPOP3-654:
-------------------------------------------

It's implemented (locally), but the {{HalfStepTraversalStrategy}} now breaks the {{PartitionProcessTest}}.

{code}
assertEquals(new Long(2), sourceCC.V(vC.id()).inE().count().next());
assertEquals(new Long(0), sourceCC.V(vC.id()).in().count().next());
{code}

The second assertion fails. (expected: 0, actual: 2), because {{in().count()}} is converted to {{inE().count()}}.

Suggestions? Should the {{PartitionStrategy}} deactivate the {{HalfStepTraversalStrategy}}?

> 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)