[TINKERPOP-2065] Optimize iterate() for remote traversals

• Type: Improvement
• Status: Closed
• Priority: Critical
• Resolution: Done
• Affects Version/s: 3.3.3
• Fix Version/s: 3.4.0, 3.3.5
• Component/s: dotnet, javascript, process, python
• Assignee: Stephen Mallette
• Reporter: Stephen Mallette
• Created: 15/Oct/18 10:46
• Updated: 05/Nov/18 16:14
• Resolved: 05/Nov/18 16:14

Description

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

Issue Links

• links to: GitHub Pull Request #984