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
Java version (OpenJDK or Oracle JDK) | Support type |
---|---|
17 | Supported with limitations:
|
Supported Java versions for launching Talend Server modules
Talend Server Module | Java version (OpenJDK or Oracle JDK) | Support type |
---|---|---|
|
|
Supported with limitations:
|
|
|
Supported The recommended Java versions for Talend MDM Server are Java 8 and 11. |
|
|
Supported |
|
|
Supported |
# export modules
export JAVA_OPTS="$JAVA_OPTS --add-opens=java.base/sun.security.x509=ALL-UNNAMED --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED"
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:
- 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 run 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 with a different Java version on a Talend JobServer which requires Java 17 to start and uses Java 17 by default for execution, you can configure a different JVM for execution.
- To run your Data Integration Jobs locally in Talend Studio or on a Talend JobServer 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.
- To run 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.
The following table shows 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 |
11 | Supported |
8 | Not supported |
Java version for execution | Support type |
---|---|
17 | Supported with limitations:
|
11 | Supported with limitations:
|
8 | Supported with limitations:
|
The execution of the Big Data Spark Jobs actually depends on the Java versions supported by the cluster.