[
https://issues.apache.org/jira/browse/TINKERPOP-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673223#comment-16673223
]
stephen mallette commented on TINKERPOP-2065:
---------------------------------------------
Yeah - it changes the whole model for python, .NET and JS and then isn't
compatible with the "remote" Gremlin Java! It may be always better to be
explicit in the traversal with {{limit(1)}} and keep {{hasNext()}} for
client-side iteration. Still trying to think of a way, but, in the mean time, I
do have {{Iterate()}} fixed at least. We can close the ticket on that basis and
open another if we think of some way to deal with {{hasNext()}} but i'm not
hopeful. We'd have to make iteration work more on-demand at the protocol level
which just isn't how it's based.
> Optimize iterate() for remote traversals
> ----------------------------------------
>
> Key: TINKERPOP-2065
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2065
> Project: TinkerPop
> Issue Type: Improvement
> Components: dotnet, javascript, process, python
> Affects Versions: 3.3.3
> Reporter: stephen mallette
> Assignee: stephen mallette
> Priority: Critical
>
> In GLVs {{iterate()}} is not implemented as it is in Java where remote
> traversals append a {{NoneStep}} to filter all results serverside and thus
> generate side-effects. -Also, {{hasNext()}} is generally under-optimized in
> remote traversals because the {{hasNext()}} check is on the client side - not
> the server. We need a similar version of {{NoneStep}} for {{hasNext()}}
> basically.-
> Nicely noted by [~Florian Hockmann] -
> https://groups.google.com/d/msgid/gremlin-users/8044fcf4-8941-4826-998b-3743154dccd2%40googlegroups.com?utm_medium=email&utm_source=footer
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
