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.002229
• The driver has been enhanced to retry API call executions when an HTTP failure or driver exception occurs. You can configure this behavior with the new RetryExceptions connection property. When this option is set to 1, the driver uses the retry value specified by the WSRetryCount connection property. Refer to RetryExceptions for details.* Available: 11/21/2023 | 6.0.0.001928.
• The driver has been enhanced to support fetching access and refresh tokens at connection when OAuth2.0 is enabled. When using the new dynamic authorization code grant, you can initiate an authorization code grant flow by specifying login credentials using the login prompt for your service, thereby providing a method to authenticate without fetching access and refresh tokens via the Configuration Manager or a third-party application. In addition, the new EnableLoginPrompt and RedirectURI properties have been added to enable this functionality. Refer to Configuring OAuth 2.0 authentication for details.* Available: 11/21/2023 | 6.0.0.001928.
• The driver has been enhanced to support the JSON and INTERVAL data types. Refer to Data types for details.* Available: 11/21/2023 | 6.0.0.001928.
• The driver has been enhanced to allow users to specify values for the following connection properties:*
  • AuthURI and TokenURI for OAuth 2.0 authentication
  • JWTAudience and TokenURI for Service Account authentication
  Earlier, these properties were hidden and their default values were used for authenticating to Google BigQuery. Refer to Configuring OAuth 2.0 authentication and Configuring service account authentication for details. 
  
• 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. Refer to Data types for details.*
  
• 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). Refer to Configuring service account authentication and ServiceAccountKeyContent for details.*
• The EnableCatalogSupport connection property has been added to the driver. It determines whether the driver supports specifying values for catalog parameters in metadata calls. Refer to EnableCatalogSupport for details.*
• The driver has been enhanced with the new PrimaryKeyPattern connection property, which allows you to determine which column in a table is designated as the primary key. Google BigQuery does not have the concept of primary keys, or even uniqueness. However, some applications will not function properly without at least one column in a table designated as the primary key. This property allows your applications that require a primary key to function correctly when connecting to Google BigQuery data sources. Refer to PrimaryKeyPattern for details.*
• 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. Refer to Google BigQuery Storage API for details.*
• 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. For details refer to SpyAttributes.*

• 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 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 value of the SchemaSet configuration property has been changed to the project and dataset specified at connection. Refer to Schema Set (Configuration Option) for details.*
• The default value of the WSRetryCount connection property has been changed to 5. Refer to WSRetryCount for details.*

NOTES, KNOWN ISSUES, and LIMITATIONS

• When using the Streaming API for insert operations, the rows are queued and appear in the table after a delay. The duration of the delay varies and can go up to 30 minutes. You must not modify the table or run other operations on the table while there are rows in the streaming queue. Changing the table's metadata or running DML operations can cause uncommitted streaming rows to be lost.
• For metadata calls, the driver returns catalog as null and schema in catalog.schema format. For example, for the following call: getTables(p1,d1,t1,null), where p1 is project, d1 is dataset, and t1 is table, the driver will return catalog as null and schema as p1.d1. Note that catalog and schema are equivalent to project and dataset in Google BigQuery.
• If the file type of the private key file used for service account authentication is .p12, the authentication will fail, unless the skipDDPKIProvider system property is set to true.

FEATURES

• Supports standard and legacy Google BigQuery SQL dialects. Refer to Standard and legacy SQL support for more information.
  
• Supports JDBC core functions. Refer to JDBC support in the Progress DataDirect for JDBC Drivers Reference.
  
• 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. Refer to JsonFormat for more information.
  
• Supports proxy connections. Refer to Connecting through a proxy server for details. 
  
• Supports the handling of large result sets with configurable paging and the FetchSize and WSFetchSize connection properties. Refer to FetchSize and WSFetchSize for details.