What's new in this release?

Support and certification

Changes Since 6.0.1 Release

• Driver 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. See FIPS (Federal Information Processing Standard) for details.
  • 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. See 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. See 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 support ACID operations for Inserts, Updates, and Deletes on servers that are configured to use them. See Restrictions for Apache Hive functionality for more information on limitations and restrictions.
  • The driver has been enhanced to support Kerberos authentication for Apache ZooKeeper. See 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 ZooKeeper Discovery and ZooKeeper Name Space connection properties. See Apache ZooKeeper, ServerName, ZooKeeperDiscovery, ZooKeeperNamespace for details.
• Changed Behavior
  • The connection property SpyAttributes has been updated to exclude the attribute load=classname, which was previously used to load the driver specified by the given class name. See SpyAttributes for details.

  • Java SE 7 has reached the end of its product life cycle and will no longer receive generally available security updates. As a result, the drivers will no longer support JVMs that are version Java SE 7 or earlier. Support for distributed versions of Java SE 7 and earlier will also end, including IBM SDK (Java Edition).

Highlights of the 6.0.1 Release

• Driver Enhancements
  • The driver has been enhanced to support the following complex data types: Array, Map, Struct, and Union. See 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. See 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.

    See 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. See 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 hive for the service name and the value of the ServerName property as the fully qualified domain name. See ServicePrincipalName for details.

Highlights of the 6.0.0 Release

• Driver Enhancements
  • 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. See Data types for details.

  • 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. See HTTP Mode,TransportMode, and HTTPPath for details.

  • 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. See Configuring user ID/password authentication, EnableCookieAuthentication, and CookieName.
  • The driver has been enhanced to support Apache Knox. See Apache Knox for details.
  • The driver has been enhanced to support Impersonation and Trusted Impersonation using the new ImpersonateUser property. See ImpersonateUser for details.
  • The BatchMechanism connection property has been added to the driver. When BatchMechanism is set to multiRowInsert, the driver executes 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. See BatchMechanism for details.
  • 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. See CatalogMode for details.
  • 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. See ArrayFetchSize and Performance considerations for details.
  • The new ArrayInsertSize connection property provides a workaround for memory and server issues that can sometimes occur when inserting a large number of rows that contain large values. See ArrayInsertSize for details.
  • The driver's Kerberos functionality has been enhanced to support SASL-QOP data integrity and confidentiality. See Kerberos SASL-QOP for details.
  • The driver has been enhanced to support SSL, incorporating the addition of nine new connection properties. See Data encryption for details.
• 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
  • 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.
    See Configuring the driver for Kerberos authentication for details.