Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Search our knowledge base, curated by global Support, for answers ranging from account questions to troubleshooting error messages.
Recent Documents
-
'Talend Data Mapper Essentials' Training Course
Talend Data Mapper helps you work with hierarchical data involving complex constructs like nested or looping structures. The product lets you define a... Show MoreTalend Data Mapper helps you work with hierarchical data involving complex constructs like nested or looping structures. The product lets you define and execute transformations (called maps) between data records or documents. You can define the input and output structures manually or import them from various formats (such as XML, SWIFT, COBOL, CSV, EDI, XLS, and MySQL databases).
This learning path familiarizes you with the most popular features of Talend Data Mapper.
- Target Audience: Data Integration developers with complex data mapping requirements.
- Prerequisites: Completion of Talend Data Integration Basics or Introduction to Talend Studio, and a general understanding of the hierarchical structures of JSON and XML.
- Badge: Complete this learning plan on your way to earning the Talend API Services Developer Practitioner badge. To know more about the criteria to earn this badge, refer to the Talend Academy Badging Program page.
- Availability: This learning plan is available as part of a Talend Academy Learning Subscription, and as a private virtual or private onsite instructor-led course.
If you are already a Talend Academy subscriber or want to access the publicly available content on the platform, go to the Talend Academy Welcome page to log in or create an account.
-
Spark Job using a tHMapFile component adds an extra newline character in the out...
Problem Description The output file generated by the tHMapFile component in Spark batch Job has an extra newline character after every record. ... Show MoreProblem Description
The output file generated by the tHMapFile component in Spark batch Job has an extra newline character after every record.
Root Cause
Creating a Flat representation adds an __osdtTerminator element at the end of the file. Also, in a Big Data environment, each output record is seen as its own file by the Flat representation. As a result, you get an extra newline character.
Solution
Remove the __osdtTerminatorelement from the file representation and clear the Output as delimited? check box in Flat representation.
-
Spark and cluster details to investigate for a TDM on Spark issue
Overview You are facing an issue on TDM on Spark. As a customer or a support engineer here are the environment details to check and collect. ... Show MoreOverview
You are facing an issue on TDM on Spark. As a customer or a support engineer here are the environment details to check and collect.
Resolution
-
Big data cluster in use: CDH, HDP, MapR, and so on
-
Component using Spark:
- Components configuration: Signature, Path and details
-
Spark configuration (Spark version, details and cluster config)
-
Spark runtime: Local or cluster (Standalone or Yarn Client)
-
-
How to isolate and replicate a TDM or a TDM on Spark issue
Overview Below are some steps that could help to isolate or replicate a TDM issue or a TDM on Spark issue. Description Check the last change don... Show MoreOverview
Below are some steps that could help to isolate or replicate a TDM issue or a TDM on Spark issue.
Description
- Check the last change done before break
- Find out what was changed in the Route/Job before issue surfaced
- Where was the change made – Structure/Mapping?
- What is after an upgrade/migration?
- Did the input document / format change?
- Scope of the issue: What works or does not work
- Is it a user/Studio/Machine specific issue?
- Is it Mapping/Structure related?
- Does it depends on a specific representation / data used?
- Size of input (in case Spark is not used)
- Connection to the cluster: check if working fine without TDM / TDM on Spark components
- Performance related issue – on Studio/Jobserver/Runtime/Cluster
- Working/non-working scenarios
- Find out if there is a specific input/use case that always fails
- Determine simplest case where problem occurs (process of elimination)
- Steps to reproduce
- Exact environment details (Talend version, Cluster details…)
- Create a mockup/sample Structure/Map/Route/Job in-house
- Customer data: get sample input/output data if it is data dependent issue
- Get the entire Job/Route (and in some cases, the project or workspace) for cases where issue cannot be easily replicated
- Check the last change done before break
-
Talend Data Mapper - Split Loop option
The purpose of this video is to show how to use the Split Loop option. The Split Loop option is useful when you want to map to a single output loop... Show More -
Talend Data Mapper - Custom Java Functions
The purpose of this video is to show you how to add custom Java functions to the Data Mapper repository, and then how to invoke the custom Java fun... Show More
