Force protocol v4 for driver connection

k8ssandra · Mar 3, 2021 · 62b975f · 62b975f
1 parent 858e0e7
commit 62b975f
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 1 deletion.
diff --git a/management-api-agent-dse-6.8/pom.xml b/management-api-agent-dse-6.8/pom.xml
@@ -32,6 +32,7 @@
     <bytebuddy.version>1.9.15</bytebuddy.version>
     <docker.java.version>3.1.5</docker.java.version>
     <driver.version>4.10.0</driver.version>
+    <junit.version>4.13.1</junit.version>
     <build.version.file>build_version.sh</build.version.file>
   </properties>
 
@@ -62,7 +63,7 @@
     <dependency>
       <groupId>junit</groupId>
       <artifactId>junit</artifactId>
-      <version>4.11</version>
+      <version>${junit.version}</version>
       <scope>test</scope>
     </dependency>
   </dependencies>

diff --git a/management-api-server/src/main/java/com/datastax/mgmtapi/UnixSocketCQLAccess.java b/management-api-server/src/main/java/com/datastax/mgmtapi/UnixSocketCQLAccess.java
@@ -137,6 +137,8 @@ public String toString()
         session = new LocalSessionBuilder(unixSocketEndpoint)
                 .withConfigLoader(DriverConfigLoader.programmaticBuilder()
                         .withDuration(DefaultDriverOption.REQUEST_TIMEOUT, Duration.of(30, SECONDS))
+                        // force protocol V4 for now
+                        .withString(DefaultDriverOption.PROTOCOL_VERSION, "V4")
                         .build())
                 .build();
     }