Qlik Talend Studio 2026-06 will move from Java 17 to Java 21

[Sonja_Bauernfeind]

To all Talend customers,

This is an advance notice that, to enhance both your security and experience, Java 21 will be required to launch Talend Studio starting with the 2026-06 release.

This change only concerns the Talend Studio desktop application. It has no impact on the Jobs and Services you build with it, which will continue being compliant with Java 17 runtime environments (and Java 8 for Big Data Jobs).

You have multiple options to make a smooth transition:

• The Talend Studio embedded upgrade mechanism (Feature Manager) will offer handling the JDK version upgrade
• Should you prefer, a new installer of Talend Studio 2026-06 with JDK 21 embedded will also be provided
• You will also be free to manually configure Talend Studio to start with JDK 21, provided you are on Talend Studio 2025-09 or higher

Additional details:

Along with this change, the June release will come with many additions from a Java version perspective:

• Talend Studio will allow building Jobs and Services for Java 21 runtimes, in addition to Java 17 runtimes. Java 17 will remain the default setup for runtimes for the time being
• Remote Engines, Cloud Engines, Dynamic Engines, Job Server, and Talend Runtime will support running Jobs and Services in Java 21, in addition to the Java versions they already support
• Talend Administration Center (TAC), Data Preparation (client-managed), Data Stewardship (client-managed), Talend SAP RFC Server, Talend Semantic Dictionary, and Talend Identity and Access Management will also support running with Java 21 in addition to Java 17

For further questions, please start a chat with us to contact Qlik Support and subscribe to the Support Blog for future updates.

Thank you for choosing Qlik,
Qlik Support

[yfujioka]

こんにちは

Java17でビルドしたジョブはJava21のJobserver、REでそのまま動きますか。
Java21のJobserver、REで動かすためTalend Studio(Java21)で再ビルドが必要になるのでしょうか。

よろしくお願い致します。

[ameyniel]

Hello,

Most of the Jobs compiled with Java 17 compliance should run as is in a Java 21 runtime (Job Server or RE). But this is indeed dependent on what your Jobs are doing.

Should you need to fix them, the version of Studio to choose only depends on the compliance version you want to build your Jobs with. Typically, in some cases, it is possible to fix a Job that does not work in a Java 21 runtime while still compiling it with Java 17 compliance.

Hope this helps.