Data Integration: known issues and known limitations
We encourage you to consult the JIRA bug tracking tool for a full list of open issues:
https://jira.talendforge.org/issues/?filter=29826
Limitation |
Description |
---|---|
|
|
Java PSU is not supported. |
Talend
is only supported on Java CPU Versions, not Java PSU. Some users reported problems using Talend Studio with Java PSU versions (such as jdk8_u92), but when reverting to a Java CPU Version (such as jdk8_u91) the problem was resolved. See also: http://www.oracle.com/technetwork/java/javase/cpu-psu-explained-2331472.html |
Collation limitation with Access | Since 6.0, the Access components in Talend Studio support only the General collation mode. |
OAuth mode in the Salesforce wizard |
To establish a Salesforce connection using OAuth2 authentication, you need first to execute a Talend Job to obtain your token file and then initialize it in the wizard. |
tFileCopy can work only with Java 8 | To prevent errors, users should run Jobs containing tFileCopy only on Java 8. |
tParallelize in the context of Routes and Data Services Jobs |
The tParallelize component is designed for Data Integration Jobs. Do not use it in the context of Data Services Jobs or Routes because it is not thread safe between parallel requests and will cause huge memory and CPU consumption. Use a Route if parallel processing is a requirement. |
Issue |
Workaround |
---|---|
If Talend Administration Center works in clustered mode (two Talend Administration Center instances located on different physical servers but connected to the same database), context values may not be available in task execution details.Some SOQL queries are not supported for the guess schema and guess query features of tSalesforceInput. | It is recommended to use shared folder in Job Conductor configuration which are available for all works in cluster mode. |