Support and certification

Visit the following web pages for the latest support and certification information.

Changes Since 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. See FIPS (Federal Information Processing Standard) for details.
    • 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 property is set to 1, the driver uses the retry value specified by the WSRetryCount connection property. See RetryExceptions for details.
    • 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. See Dynamic authorization code grant, EnableLoginPrompt, RedirectURI and for details.
    • The driver has been enhanced to support the JSON and Interval data types.

    • The driver has been enhanced to allow users to specify values for the following connection properties:

      Earlier, these properties were hidden and their default values were used for authenticating to Google BigQuery. See Configuring OAuth 2.0 authentication and Configuring service account authentication for details.
    • The driver has been enhanced to support the Google BigQuery Streaming API when executing batch inserts. This behavior can be configured using the UseStreamingInsert connection property. See Google BigQuery Streaming API 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 do 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.
    • The driver has been enhanced to support the BIGNUMERIC data type. See Data types for more information.
    • 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. See 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.
    • The driver has been enhanced to support the Google BigQuery Storage API when fetching large result sets. See Google BigQuery Storage API and Storage API properties for details.
      Note: Currently, the Storage API is supported only on Windows 64-bit, Linux 64-bit, and JVM 64-bit. If an application attempts to use the Storage API on an unsupported platform, the driver falls back to the Standard API.
  • 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 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.
    • The default value of the WSRetryCount connection option has been changed to 5.
    • The default value of the SchemaSet configuration option has been changed to the project and dataset specified at connection. For details, see SchemaSet (Configuration Option)

Highlights of 6.0.0 Release

  • The driver supports both standard and legacy Google BigQuery SQL dialects. See Standard and legacy SQL support for more information.

  • The driver supports JDBC core functions. For details, refer to JDBC support in the Progress DataDirect for JDBC Drivers Reference.

  • The driver serves as a complete pass-through driver. It leverages Google BigQuery SQL engine to execute queries.
  • The driver supports create, read, update, and delete (CRUD) operations.
  • The driver returns data for complex data types, such as Array and Struct, as JSON strings, which are easy to comprehend for the JDBC applications. See JsonFormat for more information.
  • The driver provides proxy support. See ProxyHost, ProxyPassword, ProxyPort, and ProxyUser for more information.
  • The driver supports the handling of large result sets with configurable paging and the FetchSize and WSFetchSize connection properties.