February 2014 HUG : Introduction to Tez
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

February 2014 HUG : Introduction to Tez

on

  • 1,447 views

February 2014 HUG : Introduction to Tez

February 2014 HUG : Introduction to Tez

Statistics

Views

Total Views
1,447
Views on SlideShare
1,440
Embed Views
7

Actions

Likes
0
Downloads
18
Comments
0

2 Embeds 7

https://twitter.com 6
http://www.slideee.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

February 2014 HUG : Introduction to Tez Presentation Transcript

  • 1. Tez, An Introduction Alan F. Gates Founder & Architect @alanfgates Page 1
  • 2. In The Beginning of Hadoop… ...there was MapReduce –It could handle data sizes way beyond those of its competitors –It was resilient in the face of failure –It made it easy for users to bring their code and algorithms to the data (i.e. free to program in Java instead of just SQL) © 2014 Hortonworks Page 2
  • 3. But, It Was Too Low Level © 2014 Hortonworks Page 3
  • 4. But it was too rigid © 2014 Hortonworks Page 4
  • 5. But, It Was Batch © 2014 Hortonworks Page 5
  • 6. YARN to the Rescue © 2014 Hortonworks Page 6
  • 7. Why Tez? Enable Data Processing In Many Tools •An execution engine that can be used by Hive, Pig, Cascading, and others •Right now SQL on hadoop is hot, and we want to enable that •But we also want to keep in mind that there’s a lot else to be done in Hadoop (machine learning, ETL, graph processing, etc.) and we want to open up the work we’re doing to those groups as well. © 2014 Hortonworks Page 7
  • 8. Why Tez? Span Batch and Interactive •It’s hard for customers to use different tools depending on their data size •It’s hard for applications like Hive to use different back end engines depending on the inputs and outputs © 2014 Hortonworks Page 8
  • 9. Why Tez? Preserve MapReduce Experience •MapReduce represents engineering centuries of work •Much has been learned (mostly the hard way) about scale and resiliency •We are not excited to reinvent those wheels, we would rather rebuild the vehicle on top of them © 2014 Hortonworks Page 9