1.3.0 1001

Repacked Magnitude Simba Google BigQuery JDBC to be compatible with DataGrip

========================================================================

Magnitude Simba Google BigQuery JDBC Data Connector Release Notes

========================================================================

The release notes provide details of enhancements, features, known issues, and
workflow changes in Simba Google BigQuery JDBC Connector 1.3.0, as well as
the version history.

1.3.0 ========================================================================

Released 2022-08-30

Enhancements & New Features

• [GBQJ-551] External account authentication support

  You can now configure the connector to authenticate the connection using
  an external account (workforce or workload identity federation). To do
  this, set the OAuthType property to 4, the ProjectID property to the
  desired project, and then set the workforce or workload configuration file
  to one of the following properties:

  • OAuthPvtKey
  • OAuthPvtKeyPath

  For more information, see the Installation and Configuration Guide.

• [GBQJ-543] Private Service Connect support

  You can now configure the connector to use Private Service Connect URLs. To
  do this, set the PrivateServiceConnectUris property to the desired URI. For
  more information, see the Installation and Configuration Guide.

• [GBQJ-566] Transaction API support

  The connector now supports JDBC transaction APIs. BigQuery supports
  multi-statement transactions inside a single query, or across multiple
  queries, when using sessions. For more information about transactions, see:
  https://cloud.google.com/bigquery/docs/reference/standard-sql/transactions.

  To use transaction APIs, and work with transactions across multiple
  queries, set the EnableSession property to 1. For more information about
  sessions, see:
  https://cloud.google.com/bigquery/docs/sessions-intro

• [GBQJ-542] Default project for dataset support

  The connector is now verified to use a default project for datasets. To do
  this, set the dataset_project_id property in QueryProperties of the
  connection string to the desired project. For more information, see the
  Installation and Configuration Guide and the Google BigQuery documentation:
  https://cloud.google.com/bigquery/docs/reference/rest/v2/ConnectionProperty

• [GBQJ-558] MATERIALIZED_VIEW table support

  MATERIALIZED_VIEW has been added to the list of table types. To retrieve
  the list of table types, use the getTableTypes function.

• [GBQJ-562] JSON data type support

  The connector now supports the JSON data type. For more information, see
  the Installation and Configuration Guide and the Google BigQuery
  documentation:
  https://cloud.google.com/bigquery/docs/reference/standard-sql/json-data

• [GBQJ-581] Improvements to projects.list API

  The MaxResults connection property is now applied to the projects.list
  call. This API is used when the connector requests the list of projects.

• [GBQJ-548][GBQJ-571] Third-party library updates

  The connector has been updated with the following third-party libraries:

  • google-oauth-client 1.34.1 (previously 1.33.1)
  • avro 1.11.1 (previously 1.11.0)

Known Issues
The following are known issues that you may encounter due to limitations in
the data source, the connector, or an application.

• The connector does not support parameterized types for Resultset and
  Parameter metadata.

  This is a limitation of the Google BigQuery server.

• Connector terminates when multiple connections are set to LogLevel=6.

  When multiple connections with the same LogPath directory are running with
  LogLevel set to 6, a collision might happen. This results in one of the
  connections terminating unexpectedly.

• The connector no longer supports parameters in the exception block.

  This is a limitation of the Google BigQuery server discovered on Mar 2021.

• TRACE level logs incorrectly contain stack trace for function entrances.

  When logging at the TRACE level (LogLevel=6), function entrance logs are
  generated for each function that is called. These logs incorrectly
  include a stack trace.

• Query prefixes are not supported.

  The driver does not support query prefixes. To specify whether your query
  statements are to be processed using standard SQL or legacy BigQuery SQL,
  configure the QueryDialect connection property.

  By default, QueryDialect is set to "SQL" so that the driver uses standard
  SQL syntax. To use BigQuery SQL instead, set the property to "BIG_QUERY".

• Support for ODBC Escape Sequences is limited.

  The only supported ODBC Escape Sequences are Scalar Functions of the form
  {fn func(args)} if func is supported by the Google BigQuery data source
  engine.

• When casting data, you must specify the data type according to Google
  BigQuery standards.

  When casting data to a specific data type, you must use the corresponding
  data type name shown in the "Casting" section of the Query Reference:
  https://cloud.google.com/bigquery/sql-reference/functions-and-operators#casting.

  For example, to cast the "salary" column to the INTEGER type, you must
  specify INT64 instead of INTEGER:

  SELECT position, CAST(salary AS INT64) from Employee

Workflow Changes =============================================================

The following changes may disrupt established workflows for the connector.

1.2.4.1007

Repacked Magnitude Simba driver for BigQuery 1.2.4.1007 as a single jar file.

Simba JDBC Driver with SQL Connector for Google BigQuery Release Notes

The release notes provide details of enhancements, features, known issues, and
workflow changes in Simba JDBC Driver for Google BigQuery 1.2.4, as well as
the version history.

1.2.4

Released 2020-05-11

Enhancements & New Features

• [GBQJ-321] Support for BigQuery scripting

  The driver now supports BigQuery scripting for Standard SQL. For more
  information, see "Scripting in Standard SQL" in the BigQuery documentation:
  https://cloud.google.com/bigquery/docs/reference/standard-sql/scripting

• [GBQJ-344] Support for additional passthrough query properties

  You can now pass a property through to the server by using the
  QueryProperties connection URL. For more information, see the
  Installation and Configuration Guide.

Resolved Issues
The following issues have been resolved in Simba JDBC Driver for Google
BigQuery 1.2.4.

• [GBQJ-336] In some cases, complex queries cause the driver to terminate
  unexpectedly.

• [GBQJ-354] In some cases, if you include comments between DDL statements,
  the statement executes correctly but the driver generates an empty result
  set.

• [GBQJ-357] If you use getProcedureColumns() to retrieve Array, Struct, or
  Geography types, the driver terminates unexpectedly.

• [GBQJ-354] In some cases, if you include comments between DDL statements,
  the statement executes correctly but the driver generates an empty result
  set.

• [GBQJ-310] When using the Numeric data type, the REST API does not include
  leading zeros.

  This issue has been resolved. The driver now uses the default BigQuery
  scale of 9 for Numeric data.

• [GBQJ-310] When using the Boolean or Datetime data types, there are
  discrepancies between flat and nested columns.

  This issue has been resolved. The format of Boolean and Datetime data in
  nested columns now matches the format of flat columns.

Known Issues
The following are known issues that you may encounter due to limitations in
the data source, the driver, or an application.

• TRACE level logs incorrectly contain stack trace for function entrances.

  When logging at the TRACE level (LogLevel=6), function entrance logs are
  generated for each function that is called. These logs incorrectly
  include a stack trace.

• Query prefixes are not supported.

  The driver does not support query prefixes. To specify whether your query
  statements are to be processed using standard SQL or legacy BigQuery SQL,
  you must configure the QueryDialect connection property.

  By default, QueryDialect is set to "SQL" so that the driver uses standard
  SQL syntax. To use BigQuery SQL instead, set the property to "BIG_QUERY".

• Support for ODBC Escape Sequences is limited.

  The only supported ODBC Escape Sequences are Scalar Functions of the form
  {fn func(args)} if func is supported by the Google BigQuery data source
  engine.

• When casting data, you must specify the data type according to Google
  BigQuery standards.

  When casting data to a specific data type, you must use the corresponding
  data type name shown in the "Casting" section of the Query Reference:
  https://cloud.google.com/bigquery/sql-reference/functions-and-operators#casting.

  For example, to cast the "salary" column to the INTEGER type, you must
  specify INT64 instead of INTEGER:

  SELECT position, CAST(salary AS INT64) from Employee

1.2.2.1004

Repacked Magnitude Simba driver for BigQuery 1.2.2.1004 as a single jar file.