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

Enhancements

• The installer program has been enhanced to support Azul Zulu JRE 11. As a result of this change, the installer has ended support for some of the old operating systems. The installer supports the following operating systems after the enhancement:*
  • UNIX/Linux:
    • Any operating system on a machine using a JRE that is Java SE 8 or higher (LTS version), including Oracle JDK, OpenJDK, and IBM SDK (Java) distributions.
  • Windows:
    • Windows 8.1 or higher
    • Windows Server 2012 RC2 or higher
  Important: These changes do not affect the operating system requirements of the driver.
  
• The driver has been enhanced to support authenticating with Hadoop delegation tokens. You can configure authentication with Hadoop delegation tokens using the new DelegationToken property and enhanced AuthenticationMethod property. Refer to Hadoop delegation token authentication for details*
• The driver has been enhanced with the new SASLQOP connection property. When Kerberos authentication is enabled, SASQOP allows you to specify the level of quality of protection used by the server for SASL mechanisms. Refer to SASLQOP for details.
  
• The driver has been enhanced to support using load balancing with Apache Zookeeper. When connecting through a Zookeeper listener configured with two or more Hive nodes, the driver now randomly connects to one of the Hive nodes returned, instead of always connecting to the first Hive node returned in the list. The remaining nodes are then used for failover when establishing the connection.*
• 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.

  Refer to SpyAttributes for more information.

• 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 ACID operations for Inserts, Updates, and Deletes on servers that are configured to use them. Refer to Restrictions for Apache Hive functionality for more information on limitations and restrictions.*
• The driver has been enhanced to support Kerberos authentication for
  Apache ZooKeeper. Refer to Configuring Apache ZooKeeper for Kerberos authentication for details.*
• The driver has been enhanced to support Apache ZooKeeper, which can be configured using the updated ServerName connection property and the new ZooKeeperDiscovery and ZooKeeperNameSpace connection properties. Refer to Apache ZooKeeper for details.*
• The driver has been enhanced to support the following complex data types: Array, Map, Struct, and Union. Refer to Data types for details.  
• The driver has been enhanced to support the Statement.cancel API, which allows you to cancel running queries.
  
• The new InitializationString connection property allows you to specify one or multiple SQL commands to be executed by the driver at connection. This provides a method for specifying session settings at connection, such as runtime server-side variables or timezones. Refer to InitializationString for details. 
  
• The driver has been enhanced to support the Binary data type, including the following two new connection properties:
  • MaxBinarySize allows you to specify the maximum length of fields of the Binary data type that the driver describes through result set descriptions and metadata methods.
  • BinaryDescribeType allows you to specify whether Binary columns are described as VARBINARY or LONGVARBINARY.

  Refer to Data types, BinaryDescribeType, and MaxBinarySize for details.

• The new MaxStringSize property allows you to specify the maximum length of fields of the String data type that the driver describes through result set descriptions and metadata methods. Refer to MaxStringSize for details.
  

Changed Behavior

• The ServicePrincipalName property has been updated to provide a default value. If no value is specified, the driver builds the default using the value hive for the service name and the value of the ServerName property as the fully qualified domain name. Refer to ServicePrincipalName for details.
  

Version 6.0.0

Enhancements

• The driver has been enhanced to support the Binary data type, including the following two new connection properties:*
  • MaxBinarySize allows you to specify the maximum length of fields of the Binary data type that the driver describes through result set descriptions and metadata methods.
  • BinaryDescribeType allows you to specify whether Binary columns are described as VARBINARY or LONGVARBINARY.
• The driver has been enhanced to optimize the performance of fetches.
• The driver has been enhanced to support the Char, Date, Decimal, and Varchar data types.
• The driver has been enhanced to support HTTP mode, which allows you to access Apache Hive data stores using HTTP/HTTPS requests. HTTP mode can be configured using the new TransportMode and HTTPPath connection properties.
• The driver has been enhanced to support cookie based authentication for HTTP connections. Cookie based authentication can be configured using the new EnableCookieAuthentication and CookieName connection properties.
• The driver has been enhanced to support Apache Knox.
• The driver has been enhanced to support Impersonation and Trusted Impersonation using the new ImpersonateUser property.
• The BatchMechanism connection property has been added to the driver. By setting BatchMechanism to multiRowInsert, you enable the driver to execute a single insert for all the rows contained in a parameter array. MultiRowInsert is the default setting and provides substantial performance gains when performing batch inserts.
• The new CatalogMode connection property allows you to determine whether the driver uses native catalog functions to retrieve information returned by DatabaseMetaData functions. In the default setting, the driver employs a balance of native functions and driver-discovered information for the optimal balance of performance and accuracy when retrieving catalog information.
• The new ArrayFetchSize connection property improves performance and reduces out of memory errors. ArrayFetchSize can be used to increase throughput or, alternately, improve response time in Web-based applications.
  
• The driver has been enhanced to support SSL for Apache Hive 0.13.0 and higher, incorporating the addition of nine new connection properties.*
• The driver's Kerberos functionality has been enhanced to support SASL-QOP data integrity and confidentiality.
• Support for row-level inserts has been added to the driver.
• The driver has been enhanced to support the Char, Decimal, Date, and Varchar data types.

Changed Behavior

• The driver supports the HiveServer2 protocol and higher, and as a result:
  • Support for the HiveServer1 protocol has been deprecated
    
  • The WireProtocolVersion connection property has been deprecated
    
• Added the RegisterStatementPoolMonitorMBean connection property. Note that the
  driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
  You must set RegisterStatementPoolMonitorMBean to true to register the Statement Pool Monitor and manage statement pooling with standard JMX API calls.
• For Kerberos authentication environments, the following changes have been implemented:
  • The driver no longer sets the java.security.auth.login.config system property to force the use of the installed JDBCDriverLogin.conf file as the JAAS login configuration file. By default, the driver now uses the default JAAS login configuration file for Java, unless you specify a different location and file using the java.security.auth.login.config system property.
  • The driver no longer sets the java.security.krb5.conf system property to force the use of the krb5.conf file installed with the driver jar files in the /lib directory of the product installation directory.
  Refer to “Configuring the Driver for Kerberos Authentication” in the user’s guide for details.

Version 5.1.4

Enhancements

• Support for row-level inserts has been added to the driver.

Version 5.1.2

Enhancements

• The driver has been enhanced to support the Kerberos authentication protocol with the addition of the AuthenticationMethod and ServicePrincipalName connection properties.

Version 5.1.1

GA Release Features

• Support for Apache Hive
• Returns result set metadata for parameterized statements that have been prepared but not yet executed
• Supports connection pooling
• Includes the LoginTimeout connection property which allows you to specify the amount of time the driver waits for a connection to be established before timing out the connection request
• 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.
• The driver provides support for the following standard SQL functionality:
  • Create Table and Create View
  • Insert
  • Drop Table and Drop View
  • Batches in HiveServer2 connections