March 12, 2024: What’s New in Qlik Cloud?

Refresh and change dataset for new AutoML experiment version

AutoML now enables users to change or refresh a dataset used for an experiment version from the catalog. This allows for changes in the feature list between versions and for updated rows to be used for training such as for retaining a model following evidence of drift.

Refining models

New space role that allows creating and managing schedules in managed spaces

With the new space role Can Operate, it is possible now to control who can reload data / apps in Managed Spaces or create or manage scheduled reloads at a more fine grain level. Users do no longer have to be assigned to the existing space role Can Manage for being able to reload data.

Managed space permissions for users with Professional or Full User entitlement

Qlik Talend Data Integration: Physical objects and data preview

You can now view the underlying physical objects that constitute your datasets without leaving Qlik Talend Data Integration. You also have the ability to view data samples of datasets’ physical objects. Data samples can be filtered and sorted. This feature make it easy to see and validate the shape of your data as you are designing your pipelines.

Physical objects and view data

In addition, you can also preview the result of a SQL transformation directly in Qlik Talend Data Integration. It allows you to easily validate your SQL transformation without the need to prepare and run the transform task and without leaving Qlik Talend Data Integration.

Preview SQL transformations

New and enhanced features in Qlik Talend Data Integration

The following improvements require Qlik Data Gateway – Data Movement 2023.11.4 or later. For information about how to upgrade, see Upgrading the Data Movement gateway installation.

Support for installing Data Movement gateway on Red Hat 9.x

Customers can now install Data Movement gateway on Red Hat 9.x or on any corresponding and compatible Linux distribution.

Setting up Data Movement gateway

Changes to Data Movement gateway service commands

The commands for stopping, starting and checking the status of the Data Movement gateway service have changed.

Data Movement gateway service commands

Changes to Amazon Redshift data type mapping

• The BOOLEAN data type, which was mapped to VARCHAR(1) in Amazon Redshift, will now be mapped to BOOLEAN.
• The BYTES and BLOB data types, which were mapped to VARCHAR(1) in Amazon Redshift, will now be mapped to VARBINARY (length).

Newly supported databases, database versions, and driver versions

This section lists the newly supported databases, database versions, and driver versions.

• Newly supported data source versions and editions

  The following data source versions are now supported:

  • Azure Database for MySQL – Flexible Server (Supported via the MySQL source connector)
  • MariaDB 10.4 – 10.11 (previously 10.4 and 10.5)

• Newly supported target data platforms and editions

  The following data target versions are now supported:

  • Azure Database for MySQL – Flexible Server (Supported via the MySQL target connector)
  • Databricks: Databricks 13.3 LTS and Serverless SQL Warehouse

• Newly supported SAP HANA driver version

  Customers with a SAP HANA source who want to install Data Movement gateway on Red Hat Linux 9.x, must install SAP HANA ODBC 64-bit Driver version 2.0.19 or later.

End-of-support database versions

This section provides information about end-of-support database versions.

• Support for the following data source versions has been discontinued:

  • Oracle 11.x
  • SAP HANA 1.0

Resolved issues

• Installing Data Movement gateway without providing a server password would not allow the tenant and proxy URLs to be configured in one command.
• Moving data from a Salesforce (SaaS application) data source would print a large number of redundant warnings, thereby impacting data loading performance.
• When retrieving changes for a SaaS application data source, if an error occurred retrieving changes for one of the tables, that table would be suspended and removed from the pipeline. Now, when encountering an error, the task will try to retrieve the changes up to three times before suspending the table.