Skip to main content Skip to complementary content

Talend Cloud Data Catalog and Talend Data Catalog Bridges

New features and improvements

Feature Description

Available in

Amazon Web Services (AWS) Redshift Database (via JDBC): Stored Procedure / SQL Expression Parsing / Support for names in square brackets

Added support for user whose schema does not contain Hive Metastore.

All Talend Data Catalog licenses

Talend Data Integration: multiple improvements

  • Expression parsing improved to recognize expression syntax on IFF statement.
  • Added case sensitive support in MappingExpressionParser.
  • Improved constant string processing in ELTMap component (in combination with Snowflake case-sensitive/insensitive parsing) to resolve mapping attribute harvesting.
  • Support for INTEGER constructor in Java expression parser to fix the unexpected METHOD_TOKEN .toString() on Java expression import.

All Talend Data Catalog licenses

Snowflake SQL DML (SnowQL): SQL Expression Parsing

  • Support for USING clause with several classifiers in DELETE statement.
  • Support for PIVOT classifier name.
  • Support for MERGE classifier name.
  • Talend Cloud Data Catalog Metadata Management Edition
  • Talend Data Catalog Data Governance Edition
  • Talend Data Catalog Metadata Management Edition
  • Talend Cloud Data Catalog Data Governance Edition

Snowflake (via JDBC): multiple improvements

  • Added SNOWFLAKE to getCanonicalName.
  • Functions TIMESTAMPADD and to_timestamp_ntz are defined.

All Talend Data Catalog licenses

Notable fixes

Issue Description

Available in

Amazon Web Services (AWS) Redshift Database (via JDBC): Stored Procedure / SQL Expression Parsing: missing support for SORTKEY and CALL statements

Added support for SORTKEY and CALL statements.

All Talend Data Catalog licenses

Qlik Sense Cloud: clarification needed on Qlik Sense Cloud Table Columns with Alias Names

Fixed parsing LOAD statement without FROM with alias.

All Talend Data Catalog licenses

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!