Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Talend Open Studio Cookbook

You're reading from   Talend Open Studio Cookbook Getting familiar with Talend Open Studio will greatly enhance your data handling and integration capabilities. This is the perfect reference book for beginners and intermediates with a host of practical recipes that clarify even complex features.

Arrow left icon
Product type Paperback
Published in Oct 2013
Publisher Packt
ISBN-13 9781782167266
Length 270 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Rick Barton Rick Barton
Author Profile Icon Rick Barton
Rick Barton
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Introduction and General Principles FREE CHAPTER 2. Metadata and Schemas 3. Validating Data 4. Mapping Data 5. Using Java in Talend 6. Managing Context Variables 7. Working with Databases 8. Managing Files 9. Working with XML, Queues, and Web Services 10. Debugging, Logging, and Testing 11. Deploying and Scheduling Talend Code 12. Common Mistakes and Other Useful Hints and Tips A. Common Type Conversions
B. Management of Contexts Index

Printing tMap variables

If you inspect code generated from a tMap variable, you will see that each of the expressions are converted into a line of the following format:output column = expression;.

This suggests that the expression is limited to one line of Java code.

Although this is how we would normally treat tMap expressions (in order to avoid confusion), this isn't strictly true, and there is one scenario where breaking this rule may be useful.

The scenario in question relates to tMap variables. If a tMap variable fails due to an exception in a variable expression that is itself a result of a variable expression, then the job can become quite difficult to debug.

To make it easier to see what is happening in each step, we can add a System.out.println code to an expression to print the state prior to execution of the failing step.

In this case, we simply force the expression logic in the generated code to become: output column = expression; System.out.println(output column);

This is how...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime