We are pleased to announce the release of Cloudera JDBC 2.6.17 driver for Apache Impala. The release has the following enhancements and fixes:
Enhancements and New Features
[IMPJ-547] The driver now supports CDH versions 5.11 through 5.16 and 6.0 through 6.3.
[IMPJ-493] The driver now uses version 2.10.1 of the Jackson library. Previously, the driver used Jackson version 2.9.9.
[IMPJ-516] The driver does not generate the correct syntax for character parameters in prepared statements if the length of the parameter value is greater than 510.
[IMPJ-512] getParameterMetaData() returns VARCHAR for all parameters.
[IMPJ-514] When you use the com.cloudera.impala.jdbc.DataSource class to connect with the JDBC 4.1 or 4.2 version of the driver, the driver returns a class cast exception.
[IMPJ-520] The JDBC 4.1 version of the driver fails to connect to servers that require encryption using TLS 1.2. This issue has been resolved. However, be aware that this issue still persists for the JDBC 4.0 version of the driver. For more information, see the "Known Issues" section.
The following are known issues that you may encounter due to limitations in the data source, the driver, or an application.
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.
See the Installation and Configuration Guide for the full list of workflow changes that may disrupt the established workflow of the drivers.
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.