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/08/27 16:19:45 UTC
[jira] [Updated] (TINKERPOP3-762) Allow mid-traversal V() (and E())
[ https://issues.apache.org/jira/browse/TINKERPOP3-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marko A. Rodriguez updated TINKERPOP3-762:
------------------------------------------
Fix Version/s: 3.1.0-incubating
> Allow mid-traversal V() (and E())
> ---------------------------------
>
> Key: TINKERPOP3-762
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-762
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.0.0-incubating
> Reporter: Daniel Kuppitz
> Assignee: Marko A. Rodriguez
> Fix For: 3.1.0-incubating
>
>
> We should allow mid-traversal {{V()}} and {{E()}}. It shouldn't be a technical problem, since we always know the traversal source, thus it's just a simple {{flatMap}}. Vendors could then implement mid-traversal global index lookups.
> *Example*:
> {code}
> g.V().hasLabel("company").has("name", "DataStax").in("worksFor").as("dse").
> V().hasLabel("company").has("name", "Aurelius").in("worksFor").as("ae").
> addOutE("dse", "knows", "ae", "since", "02/2015")
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)