Google Cloud Platform Component Release Notes

This page lists the main features added to the Google Cloud Platform component.

Feature Highlights

Version 2.2.0

TOOL GCS Create Folder

Creation of a new tool in the Process Palette named "TOOL GCS Create folder" to create empty folder on Google Cloud Storage.

On a Process, add the tool from the Process Palette, then drag & drop the folder from the Google Platform Metadata.

Then, run the Process.

Version 2.1.0

Support of EMF Compare

Several improvements have been made to support EMF Compare.

Version 2.0.5

This version contains several improvements and fixed issues which can be found in the complete changelog.

Version 2.0.4

Support authentication through "ApplicationDefault" mode

Google Cloud Platform Component allows to authenticate through ApplicationDefault mode.

This mode allows to retrieve automatically the credentials based on some rules defined by Google APIs.

To resume, it will search them first in a "GOOGLE_APPLICATION_CREDENTIALS" environment variable if it exists on the system, and on the current Google engine if not.

Complete rules can be found on Google reference article:

Version 2.0.3

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

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

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

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.

Version 2.0.2

TOOL GCS Put Blobs

Performance improvements when sending large files into Google Storage.

Version 2.0.1

Credentials revision

A new attribute "Credentials File Format" has been added to choose how the credentials will be provided.

For backward compatibility, the previously used "Json Key String" attribute, which has been moved to "deprecated" tab, has priority on the new format attribute.

To use the new mechanism, you must remove the value in the old attribute and then define the link.

The new format attribute is proving the two following formats:

  • Localfile: Absolute file path to the JSON private key file corresponding to the account to connect with. Note that it must be accessible by the Runtime on the file system.

  • String: JSon Access token string. This corresponds to the unencrypted content of the JSON private key file corresponding to the account to connect with.

The benefit of string format is that, instead of using a file path as with the other attribute, you specify the credentials directly in Metadata, so you do not have to store a local file somewhere that can be accessed by the Runtime.

The downside is that this attribute is stored as plain text inside the Metadata.

We advise to use it for development purposes, and to consider using the local file option instead for production environments.

Change Log

Version 2023.1.5

New Features

  • DI-8182: Third-Party library upgrade.

Bug Fixes

  • DI-8207: Google BigQuery mappings using Google Storage as temporary location are unexpectedly failing because of permission issues.

Version 2023.1.2

Bug Fixes

  • DI-7151: When the Google storage delivery repository is set in the engineParameters, the delivery name in the repository is incorrect.

  • DI-7268: Third-party library upgrade: org.json

Version 2023.1.1

Bug Fix

  • DI-7093: The hardcoded authentication mechanism has been removed from the code and the Google Application Default Credentials mechanism is used instead.

  • DI-7150: The build of deliveries fails if the path is not defined in the engineParameters.xml file.

Version 2023.1.0

New Features

  • DI-4919: The location used to run queries can now be changed using the jobsLocation parameter in the JDBC URL.

  • DI-5650: Log4j version 1 has been removed from the dependencies.

  • DI-5839: A retry mode has bee added to re-run the query when an internalerror or jobBackendError error message is returned.

  • DI-6041: Detailed information about the error is displayed when a Google Big Query job fails.

  • DI-6140: Multiple third-party libraries upgrade.

  • DI-6308: Credential values in memory can now be retrieved programmatically. This avoids storing and displaying the credential values in variables when using the string credentials mode.

  • DI-6309: The productCode() XPath function is now available.

Bug Fix

  • DI-6473: Multiple third-party libraries upgrade.

  • DI-6518: Jackson - Third-party library upgrade.

Version 5.3.7 (Component Pack)

New Features

  • DI-6308: Add new capabilities to retrieve the credentials programmatically.

Version 5.3.6 (Component Pack)

New Features

  • DI-6041: Show detailed information about the error when a Google Big Query job fails.

  • DI-5839: Google BigQuery: add a retry mode to re-run automatically the query when an 'internalerror' or 'jobBackendError' error message is returned.

  • DI-4919: BigQuery: Add the ability to change the location used to run queries.

Version 3.0.1 (Component Pack)

New Features

  • DI-5178: Google Platform - support the externalization of the "Credentials String" authentication attribute

  • DI-5176: Google Platform - support the externalization of the "Credentials Mode" authentication attribute

Bug Fixes

  • DI-5177: Google Platform - tech:credentialsFile() xpath function should automatically replace "\" by "/" to avoid unexpected errors on scripting actions

Version 3.0.0 (Component Pack)

New Features

  • DI-3701: Allow Components to contribute to Designer monitored statistics

  • DI-4508: Update Components and Designer to take into account dedicated license permissions

  • DI-4731: Rebranding: Template messages

  • DI-4962: Improved component dependencies and requirements management

Version 2.2.0 (Google Platform Component)

New Features

  • DI-1178: Process Palette - New tool "TOOL GCS Create Folder" to create empty folders

  • DI-3713: Internal change on how some libraries are built to ease maintenance

Bug Fixes

  • DI-3331: Google Cloud Storage and Google BigQuery wizards - When launching the wizard on an existing Metadata, the first step of the wizard did not automatically select the account defined in Metadata

Version 2.1.0 (Google Platform Component)

New Features

  • DI-3510: EMF compare utility - Component has been updated to support EMF Compare comparison utility

Bug Fixes

  • DI-1165: Template - "INTEGRATION Bigquery" and "Load Rdbms to BigQuery" - SQL_STAT_INSERT and SQL_STAT_UPDATE statistics were not computed and not displayed

  • DI-1277: Google BigQuery - When loading DATE (or TIME) type from Bigquery into some databases (such as PostgreSQL) an error such as the following could unexpectedly be thrown "l1_c_time is of type time without time zone but expression is of type character varying"

  • DI-3833: Google BigQuery - Randomly, the "EngineExceptionI: A class was not found in the engine" error was displayed even when the Module was complete, because there was an unexpected jar in the Module which caused conflicts, and which has now been removed

Version 2.0.5 (Google Platform Component)

New Features

  • DI-1052: The isRepeated attribute was not reversed in the metadata, to use repeated fields.

  • DI-3392: Metadata Variables - Added support of Metadata Variable in BigQuery

Bug Fixes

  • DI-2059: BigQuery Reverse - Could not reverse a dataset containing partitioned tables "No enum constant"

  • DI-3565: Template - INTEGRATION BigQuery - SQL_STAT_INSERT and SQL_STAT_UPDATE statistics were not displayed

Version 2.0.4 (Google Platform Component)

New Features

  • DI-1944: Support a new authentication mode named "applicationDefault" which searches for authentication credentials in the current environment automatically through default Google’s mechanism

  • DI-1945: Google Cloud Platform Metadata - rename "Credential" level to "Account" for clarity