We are pleased to announce the release of Cloudera JDBC 2.6.10 driver for Apache Hive The release has the following fixes and enhancements:
Enhancements and New Features
[HIVEJ-584] Updated Thrift library The JDBC 4.2 version of the driver now uses version 0.13.0 of the Thrift library. Previously, this version of the driver used Thrift version 0.12.0. The JDBC 4.0 and 4.1 versions of the driver continue to use Thrift version 0.12.0.
[HIVEJ-575] Updated Jackson library The driver now uses version 2.10.1 of the Jackson library. Previously, the driver used Jackson version 2.9.9.
[HIVEJ-577] The JDBC 4.1 version of the driver fails to connect to servers that require encryption using TLS 1.2.
[HIVEJ-578] When you invoke the JDBC 4.2 driver with the Datasource class, an exception occurs.
[HIVEJ-583] When you use the driver with the Denodo application, it returns the following error: "Could not initialize Class".
[HIVEJ-596] In some cases, Hive queries fail with the following error: "com.cloudera.hiveserver2.exceptions.ExceptionConverter.toSQLException: [JDBC Driver]Index: 4, Size: 4"
[HIVEJ-597] SQL statements using the EXISTS predicate return an error.
[HIVEJ-599] The driver returns incorrect results for decimal columns.
The following are known issues that you may encounter due to limitations in the data source, the driver, or an application.
[HIVEJ-577] The JDBC 4.0 version of the driver fails to connect to servers that require encryption using TLS 1.1 or later.
When you attempt to connect to the server, the connection fails and the driver returns an SSL handshake exception. This issue occurs only when you run the driver using Java Runtime Environment (JRE) 6.0. As a workaround, run the driver using JRE 7.0 or 8.0.
The following changes may disrupt established workflow for the drivers. In addition to changes that are already implemented in the current version of the driver, this section describes potentially disruptive changes that will be implemented in a future version of the driver, so that you can plan accordingly.
*Removing support for JDBC 4 (Java 6). As early as June 2020, the driver will no longer support JDBC 4 (Java 6). For a list of supported JDBC versions, see the Installation and Configuration Guide.
* Beginning with this release, support for JDBC 4.0 (Java 6) has been deprecated.
Support will be removed in a future release. For a list of supported JDBC versions, see the Installation and Configuration Guide.
* Beginning with this release, the driver no longer supports JDBC 3 (Java 5). For a list of supported JDBC versions, see the Installation and Configuration Guide.
As always, we welcome your feedback. Please send your comments and suggestions to the user group through ourcommunity forums. You can also file bugs through our external Jira projects onissues.cloudera.org.