An asterisk (*) indicates support that was added in a hotfix or software patch subsequent to a release.

Refer to the following resources for additional information:

• Product Compatibility Guide: Provides the latest data source and platform support information. 
• Fixes: Describes the issues resolved since general availability.  

Version 6.0.0

ENHANCEMENTS

• The driver has been enhanced to comply with FIPS standards for data encryption. As part of this enhancement, the driver was tested with FIPS 140-3 enabled using a Red Hat OpenJDK 21 on a Red Hat Universal Base Image 9 instance. Refer to FIPS (Federal Information Processing Standard) for details.*
  Available: 1/31/2025 | 6.0.0.001119
• The driver has been enhanced to support user impersonation with Kerberos authentication using the new ImpersonateUser connection property. Refer to the ImpersonateUser property for more information.
• The driver has been enhanced to support the Array data type through data type inference. For details, refer to Data Types.
• The driver has been enhanced to support proxy server connections. Refer to the Proxy server for more information.
• The driver has been enhanced to support LDAP authentication with user ID and password. Refer to the User ID and password authentication for more information.
• The driver supports Kerberos authentication. Refer to the Kerberos authentication for more information.
• The driver supports "No authentication," which allows you to connect without any authentication credentials. Refer to the No authentication for more information.

CHANGED BEHAVIOR

• The driver has been updated to remove all sensitive values from the string returned by calling getURL(). You might be impacted if your applications or tests expect these values when calling the function.*
  Available: 12/xx/2024
• The installer program now requires you to install a JRE that is Java SE 11 or higher before running the installer. In earlier versions, the JRE used by the installer program was included in the product. However, to avoid potential security vulnerabilities, the installer program no longer includes a JRE. Instead, the installer program uses the JRE in your environment to allow for the most secure version of a JRE to be used.*
  Note: This change does not affect the JVM requirements for the driver. For the latest driver requirements, refer to the Product Compatibility Guide.
  Available: 7/3/2024
• The default authentication method used by the driver has been updated to user ID/password via LDAP authentication (AuthenticationMethod=userIdPassword). See User ID and password authentication for details.

Notes, Known Issues, and Limitations

• Apache Impala is not designed for OLTP workloads and does not offer row-level updates or deletes. Apache Impala is instead designed for batch type jobs over large data sets with high latency.
• Apache Impala does not support transactions, and by default, the driver reports that transactions are not supported. However, some applications will not operate with a driver that reports transactions are not supported. The TransactionMode connection property allows you to configure the driver to report that it supports transactions. In this mode, the driver ignores requests to enter manual commit mode, start a transaction, or commit a transaction and return success. Requests to rollback a transaction return an error regardless of the transaction mode specified.
• Apache Impala Functional Limitations
  • No support for transactions
  • No support for canceling a running query
  • No support for row-level updates or deletes
  • No support for stored procedures
  • No support for auto-generated keys
• Apache Impala uses a subset of SQL and HiveQL, which provides much of the functionality of SQL, and therefore has some differences and limitations.
  • Column values and parameters are always nullable.
  • No support for row-level updates or deletes
  • Subqueries are supported, but they can only exist in the FROM and WHERE clauses.
  • No support for stored procedures
  • No ROWID support
  • No support for materialized views
  • No support for synonyms
  • Primary and foreign keys are not supported.
  • Support for indexes is incomplete.
  • A single quote within a string literal must be escaped using a \ instead of using a single quote.

  For more information, refer to the Apache Impala SQL Language Reference: https://impala.apache.org/docs/build/html/topics/impala_langref.html

• For Linux users: If you receive an error message when executing any DataDirect for JDBC shell script, make sure that the file has EXECUTE permission. To do this, use the chmod command. For example, to grant EXECUTE permission to the testforjdbc.sh file, change to the directory containing testforjdbc.sh and enter: chmod +x testforjdbc.sh.
• The driver allows PreparedStatement.setXXX methods and ResultSet.getXXX methods on Clob data types, in addition to the functionality described in the JDBC specification. The supported conversions typically are the same as those for LONGVARCHAR, except where limited by database support.

Version 5.1.4

ENHANCEMENTS

• The driver has been enhanced to include timestamp in the Spy and JDBC packet
  logs by default. If required, you can disable the timestamp logging by
  specifying the following at connection: For Spy logs, set
  spyAttributes=(log=(file)Spy.log;timestamp=no) and for JDBC packet logs,
  set ddtdbg.ProtocolTraceShowTime=false.
• Interactive SQL for JDBC (JDBCISQL) is now installed with the product. JDBCISQL is a command-line interface that supports connecting your driver to a data source, executing SQL statements and retrieving results in a terminal. This tool provides a method to quickly test your drivers in an environment that does not support GUIs.*
• The driver has been enhanced to support SSL data encryption. Refer to the readme for more information.*
• The driver has been enhanced to support the Char and Vachar data type with
  Impala 2.1 and higher. For details, refer to Data Types.
• Support for result set holdability has been added to the driver.

CHANGED BEHAVIOR

• The driver no longer registers the Statement Pool Monitor as a JMX MBean by
  default. To register the Statement Pool Monitor and manage statement pooling with
  standard JMX API calls, the new RegisterStatementPoolMonitorMBean connection
  property must be set to true. For details, refer to RegisterStatementPoolMonitorMBean.*

Version 5.1.3

GA Release Features

• Supports SQL read-write access to Cloudera Impala
• Includes the TransactionMode connection property which allows you to configure the driver to report that it supports transactions, even though Hive does not support transactions. This provides a workaround for applications which do not operate with a driver that reports transactions are not supported.
• Support for connection pooling