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

ASF GitHub Bot commented on TINKERPOP-2065:
-------------------------------------------

spmallette opened a new pull request #984: TINKERPOP-2065 iterate() now sends 
NoneStep
URL: https://github.com/apache/tinkerpop/pull/984
 
 
   https://issues.apache.org/jira/browse/TINKERPOP-2065
   
   Fixed this for python, .NET and js. This means that results will no longer 
be sent back from the server to the client (i.e. no client side iteration).
   
   Builds with `mvn clean install`
   
   VOTE +1

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


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

Reply via email to