We are pleased to announce the release of Cloudera JDBC 2.6.18 driver for Apache Impala. The release has the following enhancements and fixes:
Enhancements and New Features
- [IMPJ-561] The driver now supports Java 11.
- [IMPJ-566][IMPJ-580] Updated third-party libraries
- The JDBC 4.2 driver has been updated to use the following libraries:
- - log4j 2.13.3
- - slf4j 1.7.30
- The JDBC 4.0 and 4.1 versions of the driver continue to use the previous versions of these libraries.
- [00221973][IMPJ-569] The driver now supports the values set via the Statement.setFetchSize API call.
Resolved Issues
- [00195066][IMPJ-562] The driver converts UPSERT-SELECT to INSERT-SELECT.
- [00200861][IMPJ-568] When Impala analytic functions are used, the driver does not honor upper-case column aliases.
- [00206440][IMPJ-576][IMPJ-574] The driver logs incorrect socket timeout values.
- [00206060][IMPJ-578] When the UseNativeQuery property is set to 1 and there is a space between "comment" and "show partitions", the driver returns an error.
Known Issues
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.
Workflow Changes
See the Release Notes for the full list of upcoming workflow changes that may disrupt the established workflow of the drivers.
Getting Started with the Cloudera Driver
As always, we welcome your feedback. Please send your comments and suggestions to the user group through our community forums. You can also file bugs through our external Jira projects on issues.cloudera.org.