Product Announcements
Find the latest product announcements and version updates

[ANNOUNCE]  New ODBC Driver v2.6.7 for Apache Impala Released

[ANNOUNCE]  New ODBC Driver v2.6.7 for Apache Impala Released

Cloudera Employee

We are pleased to announce the release of Cloudera ODBC 2.6.7 driver for Apache Impala.  The release has the following fixes and enhancements:


Enhancements and New Features

  • [IMPJ-678] Reporting the maximum length of database fields. You can now specify the maximum character length that the driver reports for the names of the catalogs, columns, schemas, and tables. To do this, st the following connection properties:

    • MaxCatalogNameLen

    • MaxColumnNameLen

    • MaxSchemaNameLen

    • MaxTableNameLen

For more information, see the Installation and Configuration Guide.

  • [IMP-634] Thrift transport modes. The driver now enables you to specify the Thrift transport mode used. You can configure the driver to use binary, HTTP, or SASL transport. 

  • [00139411][IMP-668] Updated driver version information in Linux library. You can now check the Linux drivers version from the driver binary file. To do this, open the .so file in a text editor, and search for the text "$driver_version_sb$:". The drivers version number is listed after this text. 

  • [IMP-677] New name of Enable Simulated Transactions. The configuration option Enable Simulated Transactions (key name EnableSimulatedTransactions) has been renamed to Ignore Transactions (key name IgnoreTransactions). The previous key name continues to be supported for backwards compatibility.

  • [IMP-671] Updated third-party library linking for Linux. The Linux driver now statically links to the OpenSSL and ICU libraries by default. Driver builds with dynamically linked libraries continue to be available as needed. For more information about this change, contact Customer Support through

  • [00141891][IMP-645] Internal driver improvements. The driver has been updated with minor internal improvements.

  • [IMP-639] Updated default value for DisableOptimizedEncodingConverter. The DisableOptimizedEncodingConvert property is now set to true by default. This enables the driver to read and replace invalid UTF-8 characters.


Resolved Issues

  • [00142448][IMP-647] When the driver executes a dynamic or parameterized query with OFFSET, it returns an error. This issue has been resolved. The driver now correctly supports LIMIT x,y query syntax.

  • [IMP-654] When query retry is enabled, the driver does not retry queries when a transport or communication link failure occurs.

  • [00144299][IMP-660] When you insert a negative value into a TINYINT column,

  • the driver returns an error.

  • [00144389][IMP-664] When the driver prepares a query that includes a STRING column cast to a variable-length VARCHAR, a length of 32767 is always returned.

  • [IMP-670] When retrieving a DECIMAL value that contains an integer ending with 0, the driver erroneously returns SQL_SUCCESS_WITH_INFO and a truncation error.

  • [00145514][IMP-672] When the driver sets the SQLSetConnectAttr attribute SQL_ATTR_AUTOCOMMIT to SQL_AUTOCOMMIT_OFF, it terminates unexpectedly.


Known Issues

The following are known issues that you may encounter due to limitations in the data source, the driver, or an application. 


BINARY and DATE data types not supported.  BINARY and DATE are not supported data types in Impala. This also causes some values of TIME data types not to be supported either, 


Workflow Changes

The following changes may disrupt workflows from earlier versions


Version 2.6.0


  • 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.

Getting Started with the Cloudera Driver


As always, we welcome your feedback. Please send your comments and suggestions to the user group of through our community forums. You can also file bugs through our external Jira projects on