Google Cloud Platform Component Release Notes
This page lists the main features added to the Google Cloud Platform component.
Change Log
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
orjobBackendError
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.
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)
Version 2.2.0 (Google Platform Component)
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