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

Killing a job from within tJavaRow

Most jobs at some point require validation and will often need to be stopped if the data is found to be in error. In most cases, you can use tDie, however, if your error is found in a tJavaRow or tJava, then using tDie becomes quite convoluted. This exercise shows how the same results can be achieved using simple Java functionality.

Getting ready

Open the jo_cook_ch10_0150_killingJobtJavaRow job.

How to do it...

The steps for killing a job from within tJavaRow are as follows:

  1. Run the job. You will see that it fails with a null pointer exception.
  2. Change the line output_row.age = input_row.age; to the following code:
    if (input.age == null) {
      System.out.println("Fatal Error: age is null");
      System.exit(99);
    } else {
      output_row.age = input_row.age;
    }
  3. Run the job again. You will see that the job has been killed in a much more elegant fashion, as shown in the following screenshot:
    How to do it...

How it works...

System.exit is a Java kill command and as such will cause...

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