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 2018/12/17 20:14:00 UTC

[jira] [Closed] (TINKERPOP-2097) Create a DriverRemoteConnection with an initialized Client

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

stephen mallette closed TINKERPOP-2097.
---------------------------------------
       Resolution: Done
    Fix Version/s: 3.3.5
                   3.4.0

This was a really minor change - implemented via CTR on :

https://github.com/apache/tinkerpop/commit/f9d702757bbaf07a09ab13d534f2071a729610ee

> Create a DriverRemoteConnection with an initialized Client
> ----------------------------------------------------------
>
>                 Key: TINKERPOP-2097
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2097
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: driver
>    Affects Versions: 3.3.4
>            Reporter: Kevin Gallardo
>            Assignee: stephen mallette
>            Priority: Minor
>             Fix For: 3.4.0, 3.3.5
>
>
> Currently the only way to create a {{DriverRemoteConnection}} is by providing a Cluster or a Configuration, which will then initialize a {{Client}} internally. Users have to create a new {{Client}} for every {{DriverRemoteConnection}}.
> It would be convenient to add the possibility to provide an already initialized {{Client}} so that you don't cause a new connection to the server for each {{DriverRemoteConnection}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)