Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Now accepting applications for the Qlik Luminary and Partner Ambassador Programs: Apply by July 6!
RMartins
Employee
Employee

Talend Studio now connects natively to Qlik Open Lakehouse — query Iceberg-managed data directly from your existing Standard and Big Data jobs, with no manual JDBC configuration required. Learn how this integration works and what it means for your data workflows.


Native Qlik Open Lakehouse interoperability for Talend Studio

With the March release, Talend Studio introduces native support for querying Qlik Open Lakehouse datasets through Amazon Athena — available in both Standard Data Integration jobs and Spark-based Big Data workflows.

This means developers can now connect to Qlik Open Lakehouse data, execute SQL queries, and integrate results downstream the Talend job without manual JDBC configuration or custom setup.

Connecting Talend Studio to Qlik Open Lakehouse

Talend Studio now connects natively to Qlik Open Lakehouse through Amazon Athena — a SQL query engine that runs directly on top of cloud storage, enabling access to Iceberg-managed data without data movement or duplication. Developers can:

  • Access Qlik Open Lakehouse data with an out-of-the-box configuration,  no manual JDBC setup required
  • Execute SQL queries directly within Talend jobs (Standard and Big Data)
  • Integrate Qlik Open Lakehouse data into existing Talend jobs without disrupting current workflows

Reliable by Design

Connecting to Qlik Open Lakehouse from Talend Studio is straightforward by design. The integration ships with dedicated Athena configuration and input components, eliminating manual setup. Runtime validation, improved error handling, and secure credential management ensure the connection remains stable and trustworthy in production environments.

How Data is Organized in Qlik Open Lakehouse

In Qlik Open Lakehouse, data is ingested incrementally and accumulated in Apache Iceberg tables. A logical abstraction layer — implemented as Trino views — resolves those changes into a consolidated latest-state representation, which different engines can query without handling change consolidation logic directly.

This model supports two complementary data patterns:

  • Current-state access (SCD Type 1): query the latest-state view through Athena for operational and integration use cases
  • Full history access (SCD Type 2): query the underlying Iceberg tables directly for time-aware and audit analysis

Both patterns are available across Standard Data Integration and Big Data jobs in Talend Studio, enabling teams to work with Qlik Open Lakehouse data in the way that best suits their use case.

 

RMartins_0-1778184441104.png

Looking Ahead

This integration enables Talend Studio users to access Qlik Open Lakehouse data without changing their existing workflows — while aligning with modern, open-format architectures that support multiple query engines.

Athena is the first fully supported access path in this model, with a roadmap to extend support to additional engines over time. For organizations moving away from traditional data warehouses or adopting multi-engine strategies, this represents a concrete step toward a more flexible data architecture.

 

3 Comments