[
https://issues.apache.org/jira/browse/TINKERPOP-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko A. Rodriguez closed TINKERPOP-1496.
-----------------------------------------
Resolution: Won't Fix
Assignee: Marko A. Rodriguez
[~dkuppitz] can up with use cases where making "head-as" always be "select-as"
is bad. Thus, closing as "Won't Fix."
> Should a head-as("x") always be a select("x")?
> ----------------------------------------------
>
> Key: TINKERPOP-1496
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1496
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.2.2
> Reporter: Marko A. Rodriguez
> Assignee: Marko A. Rodriguez
> Labels: breaking
>
> There are two steps that treat a head of {{as("x")}} as {{select("x")}}.
> {code}
> match(as("x").out().as("y"), ...) => match(select("x").out().as("y"), ...)
> where(as("x").has("name")) => where(select("x").has("name"))
> {code}
> I don't like how these steps are "special" in this respect and I think that
> it would be elegant if a head-{{as()}} has a consistent meaning for all inner
> traversals.
> Thus, I'm wondering if we should make it such that EVERY head {{as("x")}}
> gets translated to {{select("x")}}.
> {code}
> addE("knows").to(as("x").out("mother"))
> property("name", as("x").out("mother").values("name"))
> {code}
> I believe this would be backwards compatible in the sense that there really
> isn't a reason why an inner traversal head-{{as()}} would be used to label.
> Dunno -- definitely need [~dkuppitz]/etc. feedback.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
