In Talend tDBInput component,  CLOB data types can not be handled properly when you are attempting to ingest data from source DB2 to Target one.

This article briefly introduces how to properly handle CLOB data types when ingesting from DB2 to Target using Talend.

How To

1. Write a Utils class ClobUtils with the method getClobAsString under Code-> Global Routines
   You can create your own routines according to your particular factorization needs.
   For more information, please check qlik Help Documentation about: Creating user routines
2. Use this Utils in tMap/tJavaRow component : ClobUtils.getClobAsString(row1.C1)
   You can call any function in any of the system and user routines from your Job components in order to run them at the same time as your Job. Please check Help Documentation about: Calling-routine-function-from-job

The code below is a scratch version that needs testing and rewriting.

Use this as an example to study:

==Example code: ===
package routines;
import java.sql.Clob;
import java.sql.SQLException;
import java.util.logging.Level;
import java.util.logging.Logger;
import org.apache.commons.io.IOUtils;
package routines;
import java.sql.Clob;
import java.sql.SQLException;
import java.util.logging.Level;
import java.util.logging.Logger;
import org.apache.commons.io.IOUtils;
import java.io.IOException;
import java.io.InputStream;
import java.io.StringWriter;
import java.lang.String;
public class ClobUtils {
    public static String getClobAsString(Object obj) {
        String out = null;
        if (obj != null && obj instanceof Clob) {
            out=getClobAsString((Clob) obj);
        } else {
            Logger.getLogger("ClobUtils").log(Level.FINE, "null value");
        }
        return out;
    }
    public static String getClobAsString(Clob clobObject) {
        String clobAsString = null;
        if (clobObject != null) {
            long clobLength;
            try {
                clobLength = clobObject.length();
                if (clobLength <= Integer.MAX_VALUE) {
                    clobAsString = clobObject.getSubString(1, (int) clobLength);
                } else {
                    InputStream in = clobObject.getAsciiStream();
                    StringWriter w = new StringWriter();
                    IOUtils.copy(in, w, "UTF-8");
                    clobAsString = w.toString();
                }
            } catch (SQLException e) {
                e.printStackTrace();
            } catch (IOException e) {
                e.printStackTrace();
            }
        }
        return clobAsString;
    }
}

Related Content

• https://stackoverflow.com/questions/2169732/most-efficient-solution-for-reading-clob-to-string-and-string-to-clob-in-java
  
  
• https://www.baeldung.com/java-string-character-large-object-conversion

Environment

• Talend Studio 
• Talend Data Integration 

A ESB route is failing to deploy with error message" xxx is likely to be incompatible with this Talend Runtime version, try recompiling the route with a newer Talend Studio version".

ERROR | Blueprint Event Dispatcher: 1 | b.CompatibilityBlueprintListener   73 | 332 - deployer-interceptor - 8.0.1.<Monthly Patch>-RT | Bundle cifmessagequeue.<Route Name> id : <Karaf> is likely to be incompatible with this Talend Runtime version, try recompiling the route with a newer Talend Studio version

Resolution

Ensure Runtime and Studio are at the same version and patch level.

As this issue may be occurring due to Camel 3 is out of support, please try to move up to Camel 4 to see if it get resolved.

In order to do so, please upgrade to the following versions:

• Talend Studio - R2025-02 or later
• Talend Runtime - R2025-02 or later
• Jobserver - R2025-01 or later

If you have built ESB route jobs using Talend Studio R2025-01 or previous versions which use Camel 3, please rebuild them in Talend Studio R2025-02 or later versions which use Camel 4.

Cause

This error indicates the Runtime Server and Talend Studio version are incompatible. The recent Camel upgrade for 2025-02 and beyond may be the issue. 

Talend Runtime 8.0.1-R2025-02 (Camel 4) is available as a complete installation package, this version supports only Routes and Data Services artifacts built with Talend Studio R2025-02 or later. Artifacts built with previous Studio versions are incompatible. This is due to the Camel 4 and Java 17 compiler changes that have been updated to both Runtime and Studio.

Please check if both Studio and Runtime server are patched to the same version.

Related Content 

For more information about upgrade, please refer to below Qlik Talend Release Notes

https://help.qlik.com/talend/en-US/release-notes/8.0/r2025-02-studio

https://help.qlik.com/talend/en-US/release-notes/8.0/r2025-02-talend-runtime

Environment

Talend ESB 

Due to tHttpRequest, tFileFetch and tRest components have been removed from Talend Studio 8.0 R2025-04 onwards in favor of tHTTPClient, some adjustments are required to transition to tHTTPClient if your current Talend jobs actively use the deprecated  tHttpRequest/tFileFetch/tREST/component.

This article briefly introduces how to find all jobs rely on the deprecated components for replacement purpose.

How to

1. Create a dummy job or find a Job using the related deprecated components
2. Right click on the component and choose " Find Component in Jobs" item from List and it will search all jobs that use this component.SearchComponentUsedinJobs 

Internal Investigation ID(s)

QTDI-783 - Deprecate tREST component in favor of tHTTPClient
QTDI-784 - Deprecate tFileFetch component in favor of tHTTPClient
QTDI-785 - Deprecate tHTTPRequest component in favor of tHTTPClient

Environment

Talend Studio 

You might be experiencing an issue in data formatting where input source values with leading zeros are not being reflected in the destination.

For example, a value like "00000001“  in the source may appear as ”1“ in the target

From above example, the leading zeros are not retained in the target column( unique ID in this case) when transferring data from a BigDecimal source type to a String type

Resolution

Use the following expression in the tMap Component of Talend Studio while mapping from source to destination

"String.format("%08d", row1.InputColumn.toBigInteger())"

Cause

A BigDecimal's standard canonical string representation does not include leading zeros.
Therefore, if you need to preserve leading zeros, you must explicitly format the value accordingly.

Related Content 

For more information about BigDecimal math, please refer to Oracle Official Document as below

https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/math/BigDecimal.html

Environment

Talend Studio 

Talend Data Integration 

A Talend ESB Route failed with below error when executing in studio 

org.apache.camel.processor.errorhandler.DefaultErrorHandler- Failed delivery for (MessageId:  xx on ExchangeId: xx). 
Exhausted after delivery attempt: 1 caught: org.apache.camel.TypeConversionException: Error during type conversion from type: org.apache.camel.component.file.GenericFile to the required type: java.lang.String with value GenericFile[myfile] due to java.nio.charset.MalformedInputException: Input length = 1

The Route Design looks like:

cFile →cProcessor (with the code exchange.getIn().getBody(String.class) in it) 

Resolution

1. Check the Source File at first.
2. Adapt the File Encoding accordingly
• In cFile component, go to Basic Settings and focus on Encoding
• Select the encoding type (UTF-8/ISO-8859-15/Custom) 
   

Cause

From above error message, you can see: "The java.nio.charset.MalformedInputException: Input length = 1” error in Java arises when the program attempts to decode a character sequence with a character encoding that is incompatible with the actual encoding of the input data. Specifically, "Input length = 1" indicates that a single byte or character is causing the decoding issue.

Environment

Talend ESB 

When attempting to deploy a Route in Talend Runtime, encountered the following error:

java.lang.NoClassDefFoundError: Could not initialize class org.talend.components.common.oauth.Jwt
Caused by: java.lang.NoClassDefFoundError: org/codehaus/jackson/map/ObjectMapper

Cause

Missing bundles for Jackson library.

Resolution

Launch the Karaf console (./trun) located in the <Runtime-Home>\bin directory, and then execute the following command:

list | grep Jackson

If the following bundles are not installed please install them using the command below:

bundle:install -s mvn:org.codehaus.jackson/jackson-mapper-asl/1.9.16-TALEND
bundle:install -s mvn:org.codehaus.jackson/jackson-core-asl/1.9.16-TALEND

Furthermore, you have the option to install the feature that encompasses all necessary bundles by running:

feature:install camel-jackson-avro

Environment

• Talend Studio R2025-02
• Talend Runtime R2025-02
• Azul Java 17 

When transitioning from password-based authentication to key pair authentication for Snowflake, you may encounter issues during the configuration of import models, especially when using encrypted private key files generated with OpenSSL v3. A common error observed during connection attempts is:

Fatal: MITI.MIRException: Connection to the database with URL 'jdbc❄️//.snowflakecomputing.com' failed: JWT token is invalid.

java.security.NoSuchAlgorithmException: 1.2.840.113549.1.5.13 SecretKeyFactory not available

java.security.InvalidKeyException: IOException : DER input, Integer tag error

The Java process fails to complete due to an invalid JWT token, commonly associated with unsupported key formats or missing runtime parameters.

Cause

The error typically occurs due to one or more of the following factors:

• The JDBC driver does not natively support OpenSSL v3-encrypted private keys without enabling BouncyCastle.
• Required parameters (User, Password, Private key file) are not correctly configured in the import model settings.
• Miscellaneous Java options required to support the key format were not passed to the process.

Resolution 

When using an unencrypted private key file:

User: Set to the Snowflake username.

Password: Enter the password

Private Key File: Provide the path to the unencrypted .pem file.

Miscellaneous Parameters: No additional Java options are required.

When using an encrypted private key file (e.g., OpenSSL v3-generated):

User: Set to the Snowflake username.

Password: Enter the passphrase used to encrypt the private key.

Private Key File: Provide the full path to the encrypted .pem file.

Miscellaneous Parameters: You must enable BouncyCastle support for decryption:

-Dnet.snowflake.jdbc.enableBouncyCastle=true

For further details, please refer to the official Snowflake documentation: Snowflake Key-Pair Authentication Guide.

Related Content

Qlik Talend Product: How to set up Key Pair Authentication for Snowflake in Talend Studio

Environment

• Talend Data Integration 8.0.1

After upgrading from Talend Version 7 to Version 8, you may encounter an issue where a Custom SQL function (Mixed read/write SQL) previously invoked via tDBInput component in Talend Version 7 and containing both INSERT/UPDATE and SELECT statements no longer performs the INSERT/UPDATE operations in Talend V8.

Even the function still returns data, though the changes to the target tables are not applied well as they did in Talend Version 7 before.

Resolution

Please use tDBRow and tParseRecordSet components to support the mixed read/write SQL function call

Cause

Mixed read/write SQL function execution is no longer supported via tDBInput component in the latest Studio Version.

Related Content 

tparserecordset

combining-two-flows-for-selective-output-standard-component-in-this

Environment

Talend Studio 

The primary error is displayed as follows in Studio/Remote Engine/Job Server Logs:

Error: LinkageError occurred while loading main class <job>_<version>.<job> java.lang.UnsupportedClassVersionError: <project>/<job>_<version>/<job> has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 55.0

Cause

A review of the error shows 

“…compiled by a more recent version of the Java Runtime (class file version 61.0)”  

A review of the Java Runtime class table will show what version of the Job was compiled. In this case, it's Java 17.

Resolution

Configure the Job execution on the Remote Engine/Job Server to utilize Java 17. For further details, please refer to the documentation page Remote Engine configuration guide's section on setting the JAVA execution path.

Environment

• Talend Data Integration 8.0.1

You may experience intermittent issues when accessing the Talend Administration Center (TAC), along with the following warning message if you are using MySQL as the database

Caused by: com.mysql.cj.exceptions.CJCommunicationsException: Communications link failure
Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary.

And this issue is random and sometimes can be temporarily resolved by refreshing the Talend Administration Center page.

(ConnectionImpl.java:456) at com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:246) at com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:199) at java.sql.DriverManager.getConnection(DriverManager.java:664) at java.sql.DriverManager.getConnection(DriverManager.java:247)

Resolution

1. Please download the latest MySQL driver Connector/J from this official page: https://dev.mysql.com/downloads/connector/j/
2. Load the latest MySQL driver to the Talend Administration Center lib folder
   <TomcatPath>/webapps/org.talend.administrator/WEB-INF/lib 
3. Restart Talend Administraion Center application after adding the driver 

MySQL JDBC drivers are backward compatible.

Cause

As per MySQL documentation, the driver class name has been updated from com.mysql.jdbc.Driver (deprecated) to com.mysql.cj.jdbc.Driver and using the deprecated driver may cause compatibility or communication issues.

For more information, please refer to MySql official document:

https://dev.mysql.com/doc/connector-j/en/connector-j-api-changes.html

Related Content 

installing-external-modules-manually-for-tac

Environment

Talend Administration Center 

You may encounter the following issue while trying to push code to the Bitbucket repositories from Talend Studio Application

Error: Command org.eclipse.jgit.api.PushCommand was called in the wrong state

Caused by: org.eclipse.jgit.errors.TransportException: ********.git: push not permitted
 

Resolution

As Write access is required to push code to the repository, please kindly check with the Bitbucket admin to obtain write access for the repository/project and attempt to push again.

Cause

This error typically occurs when there is no proper write access for the repository/project. For example, you may have read-only access to the repository on Bitbucket.

Environment

Talend Studio 

When using the CICD process, you may point the P2 to patch from your Artifact Repository instead of the Studio update site. Whether using a remote/proxy repository or have uploaded the patch contents to a local repository, you will encounter some error when attempting to deploy, redeploy, or patch your existing P2 deployment.

If you have setup basic authentication for your studio, Eclipse (within Studio) will require the keyring (secure storage) file and master password generated by Studio to gather the authentication credentials for the Artifact Repository and the P2. However, since the defined "secure_storage" file has references to Windows Security, if you attempt to use it on a Linux-based instance for CICD, it will fail due to the missing items. The root reason is the current existing keyring(secure storage) of Talend studio can not be used on another computer. By default, master key is generated by OS related API.

So if basic authentication is required for the P2 to reach out for patch items and there is a Linux-based CICD instance, you can try to re-generate keyring with provided master key in this way the newly generated keyring (secure storage) and master key can be shared to another computer.

Please note even this will not delete your existing secure_storage, though it is recommended to back them up for in case.

How To

1. Create a new secure storage and masterpassword file where the Windows-based Studio instance will be able to access it. Add the same or a new master password inside of your masterpassword file, this will be used on the Linux-based CICD instance later.
2. Generate secure storage file
   • Create a new master key file, for example. C:\Users\xxx\Downloads\mymaster.key and input your secret in the file.

     cat mymaster.key
     mysecretmasterkey
     

   • Update the Studio's .ini file via mapping the keyring and password flags to the newly created masterpassword file. Ensure that any references to the old keypair and password files are commented out. Once validated, save the changes.

     

3. Open Studio, and upon launching to the Project Selection Page, a prompt will appear asking for the credentials. Provide your username and password (or access token), and Studio will save/use those to pull from the Artifact Repository of choice, via the feature manager.

   

4. After choosing the project and it opens up, click the "Feature Manager" to confirm if the supplied credentials are working. If it does, the status window should show the prompt to upgrade to the (specified) patch, or the window to install features/components on the Studio instance. If the window doesn't show up or there is an authentication issue, please consult with your Artifact Repository team and validate the repo location and credentials in the "Windows/Preferences/Talend/Update Settings" area.
5. If successful, navigate to the " Window/Preferences/Eclipse/Security/"Secure Storage" area and uncheck the "Windows Integration (64 bit)" which will disable any Windows specific authentication requirements. Validate that the encryption type is desired for the environment; if different, please choose a specific version. Once confirmed, save the changes via the "Apply and Close" button. This will require a restart of the Studio.
6. The studio should restart and after logging back in, check the new keyring file specified. If there's no mentions to "Windows" reference, then the new keyring creation has been successful, and can be used on a Linux instance.
7. Copy the new files to a location where the P2 can access those files and the files are extracted to a location on the CICD instance where the P2 can access them as well.
8. Add the "-Declipse.keyring" and "-Declipse.password" flags to either the beginning of your Maven_Opts section or the first command that is deploying/updating the P2, and set the values to the files that were copied over. In the example below, the flags point to those files that were copied and extracted in the previous step.

   -Declipse.keyring=/opt/talend-801/keyring/keyring.txt 
   -Declipse.password=/opt/talend-801/keyring/masterpassword.txt

   Additionally, those files can be stored on the scheduler or an external location, and the eclipse flags can point there.
9. Run a build with the new flags, ideally with the

   -Dinstaller.clean=true

   or the specified p2 install directory cleared out.
   • If successful, the P2 should be noted in the build logs of the transfer of files from the repository set, to the P2's defined .installation files. 
   • If the authentication is not successful or the secure_storage files cannot be read by either Studio or the P2, please reach out to Qlik Support for further assistance.

Related Content 

basic-authentication-for-update-repositories-in-studio

Environment

Talend Data Integration 

Trying to connect SQL server with Azure MFA Authentication, It works fine using metadata connection. However, when the metadata connection is added to a Job, the Job fails with below error:

Failed to load MSAL4J Java library for performing ActiveDirectoryInteractive authentication.
com.microsoft.sqlserver.jdbc.SQLServerException: Failed to load MSAL4J Java library for performing ActiveDirectoryInteractive authentication.

Upon checking the modules view in Talend Studio, the MSAL4J jar is already installed.

Resolution

In the Advanced settings of the tDBConnection for the SQL Server connection, enable the option labeled "Authenticate using Azure Active Directory", and subsequently attempt to run the Job once more. Upon enabling this option, the msal4j jar will be automatically packaged during the Job build process.

Environment

• Talend Data Integration 8.0.1

When attempting to create a datasource that enables routes/services to access an Azure-based SQL Server with AD Authentication, the datasource may fail to connect. Despite providing the necessary ms__auth.dll to Runtime (either through the service or etc folder) and windows, the tesb log may still display the following error message:

"Failed": "com.microsoft.sqlserver.jdbc.SQLServerException:Failed to load MSAL4J Java library for performing ActiveDirectoryPassword authentication.

Cause

In many cases, the reason for this error is due to Runtime not having the specific library installed within it. Although they are very similar, Azure-based SQL Instances do require specific dependencies that may not be found with the regular Microsoft SQL JDBC drivers. This may affect those users who have a Runtime instance at or newer than the R2024-06 Patch.

Resolution

To address this issue, please follow these steps:

1. Remove any SQL JDBC jars that may have been copied to the <Runtime>/lib folder.
2. Use the karaf client (<Runtime>/bin/client.sh) to run "feature:install azure-msal4j" to install the bundle and library into Runtime.
3. Redeploy any affected routes/services, and verify that both the datasource and the task run as expected.

If the datasource or task is still encountering connection issues, kindly contact Qlik Support.

Environment

• Talend Cloud 8.0.1

The tFtpGet component is unable to filter and download the necessary file according to the designated filemask. In the FTP UI tool, the file is listed and displayed with uppercase characters. However, when using the same uppercase-based filemask to filter the file, no file is downloaded.

Cause

The file was saved in lowercase, but it appears in uppercase when viewed through the FTP client UI. This inconsistency between the saved filename and its displayed version in the UI indicates a case-mismatch issue in the FTP system.

Resolution

To resolve this issue, adjust the character case in the Filemask settings. Alternatively, enable the "Use Perl5 Regex Expression as Filemask" option to create a new filter that disregards case sensitivity. (This can be achieved by using "/i" in the Perl5 Regex Expression, which enables case-insensitive pattern matching, allowing "A" to match "a".)

Related Content

tFTPGet Standard properties

Perl Regular-Expressions

Environment

• Talend Data Integration 8.0.1

Question

Is it possible to use the feature "use or register a shared DB Connection" for a subjob or child job with tSnowflakeConnection like we can with other database connections?

Answer

This a new feature for tSnowflakeConnection Component. So far, it is not possible to share a SnowflakeConnection with a subjob/joblet in Talend Studio 8.0 R2025-03 or prior. This new feature will be available in Talend Studio 8.0 R2025-04 and above.

Internal Investigation ID(s)

AJira request (Internal) has been raised for this feature: QTDI-1376

Environment

Talend Data Integration 

After upgrading to v8-R2025-01/02, a Talend Job containing both tRest and tRestClient components encounters an error as shown below:

- javax.ws.rs.client cannot be resolved to a type
- The type javax.ws.rs.client.ClientBuilder cannot be resolved. It is indirectly referenced from required type org.glassfish.jersey.client.JerseyClientBuilder
- javax.ws.rs.client.WebTarget cannot be resolved to a type
- javax.ws.rs.core.Response cannot be resolved to a type
-  javax.ws.rs.client.Invocation cannot be resolved to a type
-  javax.ws.rs.WebApplicationException cannot be resolved to a type

Cause

When tRest and tRestClient components are used together within a Job, a conflict arises in the implementation of the Rest API.

Resolution 

To resolve this issue, a temporary workaround as shown below is to use tLibraryLoad to load external jar files in the beginning of Job:
tPrejob --onComponentOK-> tLibrary (javax.ws.rs-api-2.1.jar) --onComponentOK-> tLibrary (javax.annotation-api-1.3.2.jar)

Note: If the aforementioned workaround proves effective, kindly remember to remove the tLibraryLoad components after installing the Studio v8-R2025-03 patch.

Alternatively, apply the Studio v8-R2025-03 patch.

Related Content

Qlik Talend Data Integration: tRest post failed because of size limitation (Transfer-Encoding: chunked) from API

Internal Investigation ID(s) 

QTDI-1208

QTDI-1300

Environment

• Talend Data Integration 8.0.1

A talend Job is experiencing a tGoogleDriveGet permission issue during credential file initialization in Talend Administration Center Application. It works well in side of  Talend Studio.

Here is the error log below:

[ERROR] 15:55:50 org.talend.components.google.drive.runtime.GoogleDriveGetRuntime- D:\GDCredential\InterflourGDrive
[FATAL] 15:55:50 id_distributor_sellout.copy_of_getfile_v3__manohara_0_3.Copy_of_GetFile_V3__Manohara- tGoogleDriveGet_6 UNEXPECTED_EXCEPTION
org.talend.components.api.exception.ComponentException: UNEXPECTED_EXCEPTION
    at org.talend.components.google.drive.runtime.GoogleDriveGetRuntime.getFile(GoogleDriveGetRuntime.java:87) ~[components-googledrive-runtime-0.37.42.jar:?]
    at org.talend.components.google.drive.runtime.GoogleDriveGetRuntime.runAtDriver(GoogleDriveGetRuntime.java:60) ~[components-googledrive-runtime-0.37.42.jar:?]
    at id_distributor_sellout.copy_of_getfile_v3__manohara_0_3.Copy_of_GetFile_V3__Manohara.tGoogleDriveGet_6Process(Copy_of_GetFile_V3__Manohara.java:673) [copy_of_getfile_v3__manohara_0_3.jar:?]
    at id_distributor_sellout.copy_of_getfile_v3__manohara_0_3.Copy_of_GetFile_V3__Manohara$5.run(Copy_of_GetFile_V3__Manohara.java:2429) [copy_of_getfile_v3__manohara_0_3.jar:?]
Caused by: java.nio.file.AccessDeniedException: D:\Simon_Folder\GDCredential\InterflourGDrive
    at sun.nio.fs.WindowsAclFileAttributeView.getFileSecurity(WindowsAclFileAttributeView.java:89) ~[?:?]
    at sun.nio.fs.WindowsAclFileAttributeView.getOwner(WindowsAclFileAttributeView.java:122) ~[?:?]
    at sun.nio.fs.FileOwnerAttributeViewImpl.getOwner(FileOwnerAttributeViewImpl.java:91) ~[?:?]
    at com.google.api.client.util.store.FileDataStoreFactory.setPermissionsToOwnerOnlyWindows(FileDataStoreFactory.java:160) ~[google-http-client-1.38.0.jar:1.38.0]
    at com.google.api.client.util.store.FileDataStoreFactory.<init>(FileDataStoreFactory.java:80) ~[google-http-client-1.38.0.jar:1.38.0]
    at org.talend.components.google.drive.runtime.client.GoogleDriveCredentialWithInstalledApplication$Builder.<init>(GoogleDriveCredentialWithInstalledApplication.java:91) ~[components-googledrive-runtime-0.37.42.jar:?]
    at org.talend.components.google.drive.runtime.client.GoogleDriveCredentialWithInstalledApplication$BuilderWithIdAndSecret.<init>(GoogleDriveCredentialWithInstalledApplication.java:128) ~[components-googledrive-runtime-0.37.42.jar:?]
    at org.talend.components.google.drive.runtime.client.GoogleDriveCredentialWithInstalledApplication.builderWithIdAndSecret(GoogleDriveCredentialWithInstalledApplication.java:42) ~[components-googledrive-runtime-0.37.42.jar:?]
    at org.talend.components.google.drive.runtime.GoogleDriveRuntime.getCredential(GoogleDriveRuntime.java:164) ~[components-googledrive-runtime-0.37.42.jar:?]
    at org.talend.components.google.drive.runtime.GoogleDriveRuntime.getDriveService(GoogleDriveRuntime.java:178) ~[components-googledrive-runtime-0.37.42.jar:?]
    at org.talend.components.google.drive.runtime.GoogleDriveRuntime.getDriveUtils(GoogleDriveRuntime.java:186) ~[components-googledrive-runtime-0.37.42.jar:?]
    at org.talend.components.google.drive.runtime.GoogleDriveGetRuntime.getFile(GoogleDriveGetRuntime.java:66) ~[components-googledrive-runtime-0.37.42.jar:?]
    ... 3 more

Resolution

Ensure that the credential file owner matches the user who are running Jobserver to prevent permission access exceptions.

Please use the following command to set owner in Windows

icacls D:\GDCredential /setowner "SYSTEM" /t /l

Cause

The Error logs indicates that when tGoogleDriveGet component initializes the credential file, the new API design will verify the owner and modify ACL permissions. Since the credential file was configured using a non-Jobserver-running user, a permission exception occurs.  

com.google.api.client.util.store.FileDataStoreFactory.setPermissionsToOwnerOnlyWindows  
FileOwnerAttributeViewImpl.getOwner  

Environment

• Talend Data Integration 
• Talend Studio 

A Talend Job includes a tRest component that attempts to post 100kb of JSON/XML data to an API, but fails with the following error: 

tREST component fails with the error "400 , {
"failures": [
{
"field": "name",
"constraint": "Must be a string value, at least 1 character and at most 100 characters long."
},
{
"field": "fields",
"constraint": "Is required."
}
]
}"

Cause

When a Job includes both tRest and tRestClient components, tRest will use CXF implement auto to make HTTP requests. This will cause some random issues, as the CXF framework forces the use of the transfer-encoding header when the body size exceeds 4096. This will result in the post data being chunked (Transfer-Encoding: chunked), and then the server side cannot interpret the data fully as a whole. This was a previously identified defect. 

Resolution

To resolve this issue, a temporary workaround is to select the "Disable chunked encoding" checkbox on tRestClient.

Alternatively, apply the Studio v8-R2025-03 patch.

Internal Investigation ID(s) 

QTDI-1208

Environment

• Talend Data Integration 8.0.1