Book Image

Getting Started with Talend Open Studio for Data Integration

By : Jonathan Bowen
Book Image

Getting Started with Talend Open Studio for Data Integration

By: Jonathan Bowen

Overview of this book

Talend Open Studio for Data Integration (TOS) is an open source graphical development environment for creating custom integrations between systems. It comes with over 600 pre-built connectors that make it quick and easy to connect databases, transform files, load data, move, copy and rename files and connect individual components in order to define complex integration processes. "Getting Started with Talend Open Studio for Data Integration" illustrates common uses and scenarios in a simple, practical manner and, building on knowledge as the book progresses, works towards more complex integration solutions. TOS is a code generator and so does a lot of the "heavy lifting"ù for you. As such, it is a suitable tool for experienced developers and non-developers alike. You'll start by learning how to construct some common integrations tasks ñ transforming files and extracting data from a database, for example. These building blocks form a "toolkit"ù of techniques that you will learn how to apply in many different situations. By the end of the book, once complex integrations will appear easy and you will be your organization's integration expert! Best of all, TOS makes integrating systems fun!
Table of Contents (22 chapters)
Getting Started with Talend Open Studio for Data Integration
About the Author
About the Reviewers

Extracts from multiple tables

The previous extract example was based on data from a single table, but we frequently need to retrieve data from multiple tables in a denormalized form. Most modern applications that use a relational database will have a normalized structure, so, by definition, extracting data in a denormalized form will involve joining data from different tables.

In the Studio, we can join the data within the database extract component, using the database itself to do the work or outside of a component, within the job, where it is Java that does the data crunching. Let's take a look at examples of both.

Joining within the database component

Our first example is straightforward and presents an SQL query to the database component that joins two database tables. Carry out the following steps to recreate this job:

  1. Create a new job in the repository and call it DBInternalJoin.

  2. In the Repository window, expand the Metadata section, click on the DEMO_DB connection (highlighted in red...