Book Image

Apache Oozie Essentials

By : Jagat Singh
Book Image

Apache Oozie Essentials

By: Jagat Singh

Overview of this book

As more and more organizations are discovering the use of big data analytics, interest in platforms that provide storage, computation, and analytic capabilities is booming exponentially. This calls for data management. Hadoop caters to this need. Oozie fulfils this necessity for a scheduler for a Hadoop job by acting as a cron to better analyze data. Apache Oozie Essentials starts off with the basics right from installing and configuring Oozie from source code on your Hadoop cluster to managing your complex clusters. You will learn how to create data ingestion and machine learning workflows. This book is sprinkled with the examples and exercises to help you take your big data learning to the next level. You will discover how to write workflows to run your MapReduce, Pig ,Hive, and Sqoop scripts and schedule them to run at a specific time or for a specific business requirement using a coordinator. This book has engaging real-life exercises and examples to get you in the thick of things. Lastly, you’ll get a grip of how to embed Spark jobs, which can be used to run your machine learning models on Hadoop. By the end of the book, you will have a good knowledge of Apache Oozie. You will be capable of using Oozie to handle large Hadoop workflows and even improve the availability of your Hadoop environment.
Table of Contents (16 chapters)
Apache Oozie Essentials
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Packaging and continuous delivery


In this section, we will see how to package the Oozie code and deploy it in production.

The code for this section is available in the folder <BOOK_CODE_HOME>/learn_oozie/ch09/packaging.

Import the project in to your favorite editor (Eclipse/Intellij) as a Maven project.

The source code of Oozie gets deployed at two places:

  • On HDFS, where we copy all the Workflows, Coordinators, and so on.

  • On the local client machine from where we submit the jobs using the command line. All the job.properties files reside here.

If you see the code folder, we have a simple Maven project in which we have the following folder structure:

Maven project structure

We can see that the code that goes to HDFS has been written in the hdfs folder, and the code that has to be on the local client machine has been written in the client folder. Under both of them, we have a folder called apps. Under apps, we have different apps representing Oozie Workflows. I have copied one of the applications...