We are pleased to announce the release of Cloudera ODBC 2.6.9 driver for Apache Impala. The release has the following fixes and enhancements:
Enhancements and New Features
[IMP-704] Improved performance with multiple concurrent connections. The driver now retrieves data much faster in scenarios that involve multiple concurrent connections to the data store. This improves performance when working with applications such as Power BI.
[IMP-696][IMP-708][IMP-722] Updated third-party libraries. The driver has been updated to use the following libraries:
Boost 1.64.0 (previously 1.57.0)
libcurl 7.66.0 (previously 7.60.0)
Expat 2.2.9 (previously 2.2.0)
OpenSSL 1.1.1d (previously 1.1.0j)
[IMP-699] In some cases, when the driver submits a query that contains a Boolean value expression, the driver returns an "Unsupported query" error.
[IMP-724] The driver terminates unexpectedly when both of the following occur:
Multiple database drivers are loaded to the same process.
One driver unloads and calls ICU's u_cleanup() function, while another driver continues to run and tries to access the memory space that has been cleaned up.
The following are known issues that you may encounter due to limitations in the data source, the driver, or an application.
Limited Support for BINARY, DATE, and TIME data types.
BINARY is not a supported data type in Impala.
DATE is supported only when you connect to Impala version 3.3 or later.
As a result of the limitations above, some values of TIME data types are also not supported.
The following changes may disrupt workflows from earlier versions
[IMP-680] Removed support for earlier versions of Impala and CDH.
Beginning with this release, the driver no longer supports Impala 1.0.1 to 2.6 and CDH 5.0 to 5.8. For a list of support versions, see the Installation and Configuration Guide.
Minimum TLS Version
Beginning with this release, the driver requires a minimum version of TLS for encrypting the data store connection. By default, the driver requires TLS version 1.2. This requirement may cause existing DSNs and connection strings to stop working, if they are used to connect to data stores that use a TLS version earlier than 1.2.
To resolve this, in your DSN or connection string, set the Minimum TLS option (the Min_TLS property) to the appropriate version of TLS for your server. For more information, 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.