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

For a list a list of issues resolved since general availability, refer to the fixes.

Version 6.0.0 

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 fetch metadata for multiple tables parallelly at connection time. This enhancement provides performance benefits when connecting to a dataset that has a large amount of data.*
• The driver has been enhanced to use proxy server settings defined in the JVM system properties by default. If no proxy settings are defined in the connection string or data source, the driver will attempt to use the values of the http.proxyHost and http.proxyPort JVM system properties to connect to the database.*
• The driver has been enhanced to support the BIGNUMERIC data type, which maps to the DECIMAL JDBC data type.*
  
• The ServiceAccountKeyContent connection property has been added to the driver. This property allows you to specify the private key required for service account authentication without having to persist the .json or .p12 file that contains the private key (as required with the ServiceAccountPrivateKey property).*
• The EnableCatalogSupport connection property has been added to the driver. It determines whether the driver supports specifying values for catalog parameters in metadata calls.*
• The driver has been enhanced to support the Google BigQuery Storage API for fetching large result sets. The Storage API provides increased throughput and allows the driver to more efficiently manage large result sets. You can enable the driver to use the Storage API with the EnableStorageAPI connection property. You can further configure how the driver uses the Storage API with the StorageAPIThreshold and StorageAPIMinPageCount connection properties.*
• 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.*

CHANGED BEHAVIOR

• The default value of the SchemaSet configuration option has been changed to the project and dataset specified at connection.*

FEATURES

• Supports standard and legacy Google BigQuery SQL dialects 
• Supports JDBC core functions
• Serves as a complete pass-through driver that leverages Google BigQuery SQL engine to execute queries.
• Supports create, read, update, and delete (CRUD) operations.
  
• Returns data for complex data types, such as Array and Struct, as JSON strings, in a format that is easy to comprehend for JDBC applications.
• Supports proxy connections  
• Supports the handling of large result sets with configurable paging and the FetchSize and WSFetchSize connection properties