that issue might have been "fixed" in 3.4.4 but it created connection problems for CosmosDB. if you read the referenced dev list post it explains the "revert" of the "fix" and how things will proceed going forward:
https://lists.apache.org/thread.html/5a606bb428941faaac5c41c4df1526351406ec1ca90574dc9ced7fcd@%3Cdev.tinkerpop.apache.org%3E in short, we will not support the functionality of TINKERPOP -2289 so there is nothing to "fix". If you are using CosmosDB then you should use 3.4.3 until 3.4.5 releases (or use the 3.4.5-SNAPSHOT. Skip 3.4.4. On Tue, Nov 26, 2019 at 10:39 AM sabarish v <[email protected]> wrote: > I just curious this issue is affected in 3.4.3 and fix is applied on > 3.4.4, that is how https://issues.apache.org/jira/browse/TINKERPOP-2289 > it is mentioned. If you don't mind could you please clarify it? > > On 2019/11/26 11:30:30, Stephen Mallette <[email protected]> wrote: > > This is the issue: > > > > https://github.com/apache/tinkerpop/pull/1213 > > > > I would probably use 3.4.3, until 3.4.5 is released in the next month or > so. > > > > On Tue, Nov 26, 2019 at 6:29 AM sabarish v <[email protected]> > wrote: > > > > > Hi all, with relevant to the below JIRA, > > > https://issues.apache.org/jira/browse/TINKERPOP-2316 > > > I would like to whats the issue in the latest driver 3.4.4 with cosmos > db? > > > Then how to find the matched driver version of the server? > > > > > >
