Skip to main content Skip to complementary content

Talend Cloud Data Catalog and Talend Data Catalog Bridges

New features and improvements

Feature Description

Microsoft Azure Purview (Data Catalog) export / SAP HANA JDBC / Calculation Views: Wrong path

Enabled Calculation Views for SAP HANA.

Added packages hierarchy to the calculation view qualified name.

Qlik Replicate / Documentation / Supported Versions

Updated Qlik Replicate supported version.

Qlik Replicate: Host parameter

Updated the documentation for the Host import parameter.

Improved implementation of testing feature.

Oracle JDBC / Add new support for Oracle PL/SQL Syntax 'ISTAGG(DISTINCT ON OVERFLOW TRUNCATE)'

Improvement for LISTAGG function.

Excel File Lineage: Enable in conf/ModelBridgeList.xml

Enabled Excel File Lineage bridge.

Qlik Sense: Lineage between two applications is broken

Improvements for classifier name in FROM clause.

Fixed case when connection name has single quotes in LOAD FROM statement like FROM lib://'JAPFA_POC (inw14edc01_qsadmin)'\QVD\JAPFA_SF_Countries.QVD (qvd).

Erwin Data Modeler import/export / Support for Databricks

Added support for Databricks schemas (Databases).

Excel File Lineage / Open imported Model / Query failed with error: 400

Fixed a SolrException when a backslash was used in a search text.

Microsoft Power Query based Excel (XLSX) / Logo: Improved Excel logo

Added or updated bridge icons.

Microsoft Power Query based Excel/ Profile: Icons

Added new Excel icons to the MM installers.

IBM IIS export / Microsoft Power BI file: How to specify or modify the BI folders name during Power BI model import

Added -pbi.folder miscellaneous option to override name for single model import.

How to use -pbi.folder <folder name>.

Override the folder name for a single model, for example -pbi.folder "NewName".

Microsoft Power Query based Excel (XLSX): Renamed the bridge

Renamed Excel Lineage bridge.

SAP S/4HANA / ECC and SAP Business Warehouse / Security: SAP Java Connector API improvement

The SAP ECC and Business Warehouse bridges use the Java Connector (JCo) API to connect to a remote server. This API supports 2 ways of connecting to the server.

Based on a JCoDestination temporary file which contains all connection parameters/values. This mode is widely used in tutorials, as default mode. This mode persists connection parameters on disk at least for a few moments, which may not be desirable.

Based on a custom implementation of DestinationDataProvider which keeps connection parameters/values in JRE memory (does not use a temporary file on disk). This mode will switch to default.

Note that this is independent of the extra -jco.file miscellanous option which is still supported, for example for secure connection (SNC encryption) use cases.

Qlik Sense: All applications are extracted if you select one Stream filter having 3 applications

Fixed filtering by Stream parameter for name|id| format if applications do not belong to any stream.

Microsoft Purview export / SAP Business Warehouse 4 HANA: New support

SAP R/3 bridge:
  • Updated ABAP Function Module.
  • Improved profile, generated datatypes.
  • Improved documentation tooltip.
SAP Business Warehouse bridge:
  • Updated ABAP Function Module and added Business Warehouse 4 HANA ABAP function module.
  • Improved profile, generated datatypes, removed password properties.
  • Improved documentation tooltip.

Notable fixes

Issue Description

SAP S/4HANA, ECC / With SNC /MBCM_F0029 java.lang.IllegalArgumentException: Illegal Argument: Cannot add self as Namespace Element to Namespace

Added code to prevent adding self as child.

Fixed validation error which was the result of the previous fix.

Google Cloud Storage / Data Mapping Script: Source detail missing

Fixed root element's missing "/" after a protocol.

Set the full file path as File Directory name.

Qlik Sense: Cannot read the array length because "a" is null

Added check if list Files returns null and also added more debug messages.

Snowflake Database (via JDBC): Asset count mismatch

Fixed in JavaScript stored procedure parser.

SAP HANA Database (via JDBC): Import failed "...No suitable driver found for jdbc:sap://..."

Changed documentation for 'Driver location'.

Erwin Data Modeler / Upgrade from 11.0 to 11.1: The Arguments in the stored procedures are not extracted

Fixed for Erwin Data Modeler in operation parser.

Talend Data Integration / Migration from 11.0 to 11.1: Snowflake Connection name changes

Resolved the connection using an alias property in case the name of the connection is changed during re-import. You need to delete the Talend Data Integration Model version which has the connection problem and re-import the model after installing the patch. Talend Project metadata tree processing fix.

Qlik Replicate: File connection is not showing correctly

Improved modeling of file endpoint connections.

Improved connection name format. The name includes the name of the database and schema if the metadata contains information about them.

Qlik Replicate: Wrong connection type for Cloudera

Cloudera endpoint connectivity modeling includes HDFS and Hive connections.

Qlik Sense / Documentation: Miscellaneous parameter option -backup removes data from QVD files

Updated the bridge description.

-backup option in the _Miscellaneous_ bridge parameter, then the -backup results will place QVD files without data in the -backup result.

Snowflake Access History: Response is in a different format than the Snowflake Database (via JDBC) bridge

Added DIRuntimeContent and profile for Snowflake Access History.

Added filtering by stored procedure name. The user should use Accessed Database Objects bridge parameter to do so.

Added basic support on the Purview export bridge side.

Added unique identifier for stored procedure. This identifier is generated based on fully qualified stored procedure name and stored procedure arguments, and put it to NativeId (as it was done in Snowflake Database (via JDBC) bridge).

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!