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/04/10 19:22:13 UTC
[jira] [Closed] (TINKERPOP3-601) Consider to get rid of .back()
[ https://issues.apache.org/jira/browse/TINKERPOP3-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marko A. Rodriguez closed TINKERPOP3-601.
-----------------------------------------
Resolution: Done
Assignee: Marko A. Rodriguez (was: Daniel Kuppitz)
This has been completed.
There are two primary benefits for using {{select()}} over {{back()}}.
* {{select()}} will try and NOT use path-calculations if possible in OLTP.
* {{select()}} supports {{by()}} modulation.
Note that all the {{BackTest}} tests were simply cut/paste to {{SelectTest}} and "back" renamed to "select". All tests pass except for on in OTLP (only) that [~dkuppitz] is currently looking into (has to do with nesting selects and related to trying to avoid path calculations -- that reasoning algorithm needs some tweaking it seems).
The documentation has been updated. One less step is one less thing to worry about.
> Consider to get rid of .back()
> ------------------------------
>
> Key: TINKERPOP3-601
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-601
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process
> Reporter: Daniel Kuppitz
> Assignee: Marko A. Rodriguez
> Fix For: 3.0.0.GA
>
>
> Consider to get rid of {{.back()}} in favor of {{.select()}}. There's a discussion on the mailing list that points out differences in the behavior of both steps, which should be taken into account since some people may rely on those differences.
> https://groups.google.com/d/msg/gremlin-users/UnYK2lzXlkA/1IF4nZ__D9AJ
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)