Welcome Guest! Log in


This article describes the principal changes of Google BigQuery Component.

The plugin download section can be found at this page.

Note:

Stambia DI is a flexible and agile solution. It can be quickly adapted to your needs.

If you have any question, any feature request or any issue, do not hesitate to contact us.

 

This article is dedicated to Stambia DI 2020 (S20) or higher.

If you are using Stambia DI S17, S18 and S19 please refer to this article for Google BigQuery Addon or to this article for Google BigQuery Templates.

 

component.google.bigquery.2.0.4

Prerequisistes

  • Stambia DI Designer 2020 (S20.1.0) or higher

 

When you are working with Google Cloud BigQuery Metadata, you need to define the Google Cloud Platform Credentials to be able to perform operations.

A new step in the BigQuery wizard has been added to propose selecting the corresponding credentials, which will be displayed when creating a new BigQuery Metadata or when launching the wizard from an existing Metadata.

This wizard has been added to ease the configuration and usability of Google BigQuery Metadata.

 

Note that the credentials proposed in this wizard are retrieved from all Google Cloud Platform Metadata of current workspace, in which credentials are defined.

All existing credentials are displayed automatically.

Just select one and click on Next to continue to the next step.

 

BigQ01

 

 

component.google.bigquery.2.0.3

Fixed issue with join

When perfoming joins between BigQuery tables or stages in a Mapping, generated join query was not correct in some situations, causing errors at execution.

 

component.google.bigquery.2.0.2

Prerequisites:
  • Google Cloud Platform Component 2.0.2 or higher

 

REJECT BigQuery

All constraints verifications are now performed in a single instruction, to limit the number of requests.

We modified this to avoid reaching the query limits of Google BigQuery APIs.

 

Load RDBMS to BigQuery

When the work schema is different from the target schema, the load jobs did not load the table in the correct location.

 

Load Google Cloud Storage Json to BigQuery

New option SuccessIfNoFile

Adding a new option : SuccessIfNoFile.

When set to 'true' the LOAD template will not fail if source file(s) is(are) do not exist and will create an empty table based on the expected structure.

This allows to continue processing even when there is no source data, for instance.

 

Fix work schema usage

When the work schema is different from the target schema, the load jobs did not load the table in the correct location.

 

component.google.bigquery.2.0.1

Prerequisites:
  • Google Cloud Platform Component 2.0.1 or higher

 

Credentials and Project ID

A new attribute to drag and drop a Google Cloud Platform Credentials Metadata node on the BigQuery Metadata has been added, to replace the usage of 'credentialsFile' and 'projectId' properties which are now deprecated.

Note that for backward compatibility, when properties are defined they have priority on the new credentials link.

To use the new mechanism, you must remove the properties and then define the link.

 

Refer to this article for more information.

 

Temporary Bucket

A new attribute to drag and drop a Google Cloud Storage Bucket Metadata node has been added, to replace the default storage bucket attribute which is now deprecated.

Note that for backward compatibility, when the old attribute is defined, it has priority on the new storage link.

Note that old attribute has been moved under deprecated tab.

 

Refer to this article for more information.

 

Fix issue with Bigint

This version fixes an issue which was causing an SQLFeatureNotSupportedException in mapping using BigInt as source.

 

Fix issue with credentials error message

This version fixes an issue which was causing unclear and misleading error message when the credentials were the defined or incorrectly.

 

You have no rights to post comments

Articles

Suggest a new Article!