You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2015/06/30 17:57:06 UTC

[jira] [Closed] (TINKERPOP3-734) Driver uses polling tying up threads

     [ https://issues.apache.org/jira/browse/TINKERPOP3-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette closed TINKERPOP3-734.
---------------------------------------
       Resolution: Done
    Fix Version/s: 3.0.0.GA

I've run about a billion requests over these changes and have not seen anything bad introduced - merged to master.

> Driver uses polling tying up threads
> ------------------------------------
>
>                 Key: TINKERPOP3-734
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-734
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: driver
>            Reporter: Adrian Gonzalez
>            Assignee: stephen mallette
>             Fix For: 3.0.0.GA
>
>
> The driver uses polling to return ResultSet.one() and for the CompletableFuture in ResultSet.all().
> Ideally polling should not be necessary when using Netty and CompletableFutures.  This causes problems when trying to use it with a framework like [vert.x|http://vertx.io/].
> Could you consider an approach more similar to the Cassandra driver from datastax?
> https://github.com/datastax/java-driver
> See [Session.executeAsync()|https://github.com/datastax/java-driver/blob/2.1/driver-core/src/main/java/com/datastax/driver/core/Session.java#L166] which is equivalent to gremlin-driver Client.submitAsync().



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)