Compatible Java Environments
The following tables provide information on the recommended Java Environment to use with your Talend product from May 2024 and later. If you are using Talend 8.0 products that were not patched nor updated with the May 2024 updates or later ones, see Compatible Java Environment before May 2024.
The supported Java platforms are OpenJDK and Oracle JDK. The recommended distribution for OpenJDK is Zulu.
In the following documentation:
- Recommended: designates an environment recommended by Qlik based on experience and customer usage.
- Supported: designates a supported environment for use with the listed component or service.
- Supported with limitations: designates an environment that is supported by Qlik but with certain conditions explained in notes.
Supported Java versions for launching Talend Studio
The supported Java versions to launch Talend Studio are different for 8.0 and 7.3.
| Java version (OpenJDK or Oracle JDK) | Support type |
|---|---|
| 17 | Supported with limitations:
|
| Java version (OpenJDK or Oracle JDK) | Support type | Notes |
|---|---|---|
| 11 | Recommended | When running Oracle 11, Talend Studio should conform to JDK Compiler Compliance Level 11 (default). |
| 8 | Supported | When running Oracle 8, Talend Studio should conform to JDK Compiler Compliance Level 1.8 (default). If the installed JDK version is lower than 1.8.0_161, you need to also install the additional resource Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. This is also applicable to the execution of standalone Jobs. |
Supported Java versions for launching Talend Server modules
| Talend Server Module | Java version (OpenJDK or Oracle JDK) | Support type |
|---|---|---|
|
|
Supported with limitations:
|
|
|
Supported with limitations:
|
|
|
Supported |
|
|
Supported |
Supported Java versions for running Talend artifacts
The Java version that you use to launch Talend modules and the Compiler Compliance Level of Jobs can be different. The Compiler Compliance Level corresponds to the Java version used for the Job code generation. For more information, see Setting up Java in Talend Studio.
Pay attention to the following before working with Java 17:
- If your Talend Studio has been launched with Java 11, after installing the 8.0 R2023-10 Talend Studio monthly update or a later one, Talend Studio keeps the same behavior as before. You must set the Java interpreter in Talend Studio to Java 8 if you want to execute your Jobs with Java 8. For more information, see Java Interpreter path (Talend).
- After installing the 8.0 R2023-10 Talend Studio monthly update or a later one, if you switch the Java version to 17 and
relaunch your Talend Studio with Java 17:
- To execute your Data Integration Jobs locally in Talend Studio, activate the Enable Java 17 compatibility
option on the view in the Talend Studio
Project Settings dialog box.
If your Jobs include any custom components that require access to the Java internal modules, you need to configure them manually after activating the Enable Java 17 compatibility option. For more information, see Setting up Java in Talend Studio.
Information noteWarning: With the Enable Java 17 compatibility option activated, any Job built by Talend Studio cannot be executed with Java 8. For this reason, verify the Java environment on your Job execution servers before activating the option. - To run your Data Integration Jobs on a Remote Engine v2.13 onwards,
which requires Java 17 to start and uses Java 17 by default for
execution, you have two options:
- Rebuild your Jobs: activate the Enable Java 17 compatibility option on the view, following the same process as explained above for running Jobs locally in Talend Studio. This is the recommended approach. This approach allows you to run those Jobs with the default Java 17 version of Talend Remote Engine.
- If you prefer not to rebuild your Jobs, configure the engine to use a different Java version from its default. To do this, specify the Java 8 or 11 instances to be used when installing the engine using the installer, or manually modify a configuration file after the installation.
- To execute your Data Integration Jobs locally in Talend Studio or on a Remote Engine which is running on Java 8, you must set the Java interpreter in Talend Studio to Java 8 and deactivate the Enable Java 17 compatibility option on the view in the Talend Studio Project Settings dialog box. For more information, see Java Interpreter path (Talend) and Setting up Java in Talend Studio.
- You can execute Jobs compliant with Java 11 with a Cloud Engine. If your existing Jobs still require Java 8 on Cloud Engine, you can set up a rollback configuration using these endpoints to ensure your Cloud Engines continue to use Java 8.
- To execute your Data Integration Jobs locally in Talend Studio, activate the Enable Java 17 compatibility
option on the view in the Talend Studio
Project Settings dialog box.
When executing artifacts with Java 11, it is recommended to activate the Enable Java 17 compatibility option so that you can later execute these artifacts with Java 17.
The following tables show in which Java environments the corresponding item can be executed.
| Java version for execution | Support type |
|---|---|
| 17 | Supported with limitations:
|
| 11 | Supported with limitations:
|
| 8 | Supported with limitations:
|
| Java version for execution | Support type |
|---|---|
| 17 | Supported with limitations:
|
| 11 | Supported |
| 8 | Not supported |
| Java version for execution | Support type |
|---|---|
| 17 | Supported with limitations:
|
| 11 | Supported |
| 8 | Supported with limitations:
|
The execution of the Big Data Spark Jobs actually depends on the Java versions supported by the cluster.