HbaseHivePigbyRohitDubey

NoSQL and Big Data Processing
Hbase, Hive and Pig, etc.
Presented By Rohit Dubey

History of the World, Part 1
 Relational Databases – mainstay of business
 Web-based applications caused spikes
 Especially true for public-facing e-Commerce sites
 Developers begin to front RDBMS with memcache or
integrate other caching mechanisms within the application
(ie. Ehcache)

Scaling Up
 Issues with scaling up when the dataset is just too big
 RDBMS were not designed to be distributed
 Began to look at multi-node database solutions
 Known as ‘scaling out’ or ‘horizontal scaling’
 Different approaches include:
 Master-slave
 Sharding

Scaling RDBMS – Master/Slave
 Master-Slave
 All writes are written to the master. All reads performed
against the replicated slave databases
 Critical reads may be incorrect as writes may not have been
propagated down
 Large data sets can pose problems as master needs to
duplicate data to slaves

Scaling RDBMS - Sharding
 Partition or sharding
 Scales well for both reads and writes
 Not transparent, application needs to be partition-aware
 Can no longer have relationships/joins across partitions
 Loss of referential integrity across shards

Other ways to scale RDBMS
 Multi-Master replication
 INSERT only, not UPDATES/DELETES
 No JOINs, thereby reducing query time
 This involves de-normalizing data
 In-memory databases

What is NoSQL?
 Stands for Not Only SQL
 Class of non-relational data storage systems
 Usually do not require a fixed table schema nor do they
use the concept of joins
 All NoSQL offerings relax one or more of the ACID
properties (will talk about the CAP theorem)

Why NoSQL?
 For data storage, an RDBMS cannot be the be-all/end-all
 Just as there are different programming languages, need
to have other data storage tools in the toolbox
 A NoSQL solution is more acceptable to a client now than
even a year ago
 Think about proposing a Ruby/Rails or Groovy/Grails
solution now versus a couple of years ago

How did we get here?
 Explosion of social media sites (Facebook, Twitter)
with large data needs
 Rise of cloud-based solutions such as Amazon S3
(simple storage solution)
 Just as moving to dynamically-typed languages
(Ruby/Groovy), a shift to dynamically-typed data with
frequent schema changes
 Open-source community

Dynamo and BigTable
 Three major papers were the seeds of the NoSQL
movement
 BigTable (Google)
 Dynamo (Amazon)
• Gossip protocol (discovery and error detection)
• Distributed key-value data store
• Eventual consistency
 CAP Theorem (discuss in a sec ..)

The Perfect Storm
 Large datasets, acceptance of alternatives, and
dynamically-typed data has come together in a perfect
storm
 Not a backlash/rebellion against RDBMS
 SQL is a rich query language that cannot be rivaled by the
current list of NoSQL offerings

CAP Theorem
 Three properties of a system: consistency, availability and
partitions
 You can have at most two of these three properties for any
shared-data system
 To scale out, you have to partition. That leaves either
consistency or availability to choose from
 In almost all cases, you would choose availability over
consistency

The CAP Theorem
Consistency
Partition
tolerance
Availability

The CAP Theorem
Once a writer has written,
all readers will see that
write
Consistency
Partition
tolerance
Availability

Consistency
 Two kinds of consistency:
 strong consistency – ACID(Atomicity Consistency
Isolation Durability)
 weak consistency – BASE(Basically Available Soft-
state Eventual consistency )

ACID Transactions
 A DBMS is expected to support “ACID transactions,”
processes that are:
 Atomic : Either the whole process is done or none is.
 Consistent : Database constraints are preserved.
 Isolated : It appears to the user as if only one process executes at
a time.
 Durable : Effects of a process do not get lost if the system crashes.
16

Atomicity
 A real-world event either happens or does
not happen
 Student either registers or does not register
 Similarly, the system must ensure that either
the corresponding transaction runs to
completion or, if not, it has no effect at all
 Not true of ordinary programs. A crash could
leave files partially updated on recovery
17

Commit and Abort
 If the transaction successfully completes it
is said to commit
 The system is responsible for ensuring that all
changes to the database have been saved
 If the transaction does not successfully
complete, it is said to abort
 The system is responsible for undoing, or rolling
back, all changes the transaction has made
18

Database Consistency
 Enterprise (Business) Rules limit the
occurrence of certain real-world events
 Student cannot register for a course if the current
number of registrants equals the maximum allowed
 Correspondingly, allowable database states
are restricted
cur_reg <= max_reg
 These limitations are called (static) integrity
constraints: assertions that must be satisfied
by all database states (state invariants).
19

Database Consistency
(state invariants)
 Other static consistency requirements are
related to the fact that the database might
store the same information in different ways
 cur_reg = |list_of_registered_students|
 Such limitations are also expressed as integrity
constraints
 Database is consistent if all static integrity
constraints are satisfied
20

Transaction Consistency
 A consistent database state does not necessarily
model the actual state of the enterprise
 A deposit transaction that increments the balance by
the wrong amount maintains the integrity constraint
balance  0, but does not maintain the relation between
the enterprise and database states
 A consistent transaction maintains database
consistency and the correspondence between the
database state and the enterprise state (implements
its specification)
 Specification of deposit transaction includes
balance = balance + amt_deposit ,
(balance is the next value of balance)
21

Dynamic Integrity Constraints
(transition invariants)
 Some constraints restrict allowable state
transitions
 A transaction might transform the database
from one consistent state to another, but the
transition might not be permissible
 Example: A letter grade in a course (A, B, C, D,
F) cannot be changed to an incomplete (I)
 Dynamic constraints cannot be checked
by examining the database state
22

Transaction Consistency
 Consistent transaction: if DB is in consistent
state initially, when the transaction completes:
 All static integrity constraints are satisfied (but
constraints might be violated in intermediate states)
• Can be checked by examining snapshot of database
 New state satisfies specifications of transaction
• Cannot be checked from database snapshot
 No dynamic constraints have been violated
• Cannot be checked from database snapshot
23

Isolation
 Serial Execution: transactions execute in sequence
 Each one starts after the previous one completes.
• Execution of one transaction is not affected by the
operations of another since they do not overlap in time
 The execution of each transaction is isolated from
all others.
 If the initial database state and all transactions are
consistent, then the final database state will be
consistent and will accurately reflect the real-world
state, but
 Serial execution is inadequate from a performance
perspective
24

Isolation
 Concurrent execution offers performance benefits:
 A computer system has multiple resources capable of
executing independently (e.g., cpu’s, I/O devices), but
 A transaction typically uses only one resource at a time
 Hence, only concurrently executing transactions can
make effective use of the system
 Concurrently executing transactions yield interleaved
schedules
25

Concurrent Execution
26
T1
T2
DBMS
local computation
local variables
sequence of db
operations output by T1op1,1 op1.2
op2,1 op2.2
op1,1 op2,1 op2.2 op1.2
interleaved sequence of db
operations input to DBMS
begin trans
..
op1,1
..
op1,2
..
commit

Durability
 The system must ensure that once a transaction
commits, its effect on the database state is not
lost in spite of subsequent failures
 Not true of ordinary programs. A media failure after a
program successfully terminates could cause the file
system to be restored to a state that preceded the
program’s execution
27

Implementing Durability
 Database stored redundantly on mass storage
devices to protect against media failure
 Architecture of mass storage devices affects
type of media failures that can be tolerated
 Related to Availability: extent to which a
(possibly distributed) system can provide
service despite failure
• Non-stop DBMS (mirrored disks)
• Recovery based DBMS (log)
28

Consistency Model
 A consistency model determines rules for visibility and
apparent order of updates.
 For example:
 Row X is replicated on nodes M and N
 Client A writes row X to node N
 Some period of time t elapses.
 Client B reads row X from node M
 Does client B see the write from client A?
 Consistency is a continuum with tradeoffs
 For NoSQL, the answer would be: maybe
 CAP Theorem states: Strict Consistency can't be achieved at
the same time as availability and partition-tolerance.

Eventual Consistency
 When no updates occur for a long period of time,
eventually all updates will propagate through the
system and all the nodes will be consistent
 For a given accepted update and a given node,
eventually either the update reaches the node or
the node is removed from service
 Known as BASE (Basically Available, Soft state,
Eventual consistency), as opposed to ACID

The CAP Theorem
System is available during
software and hardware
upgrades and node
failures.
Consistency
Partition
tolerance
Availability

Availability
 Traditionally, thought of as the server/process
available five 9’s (99.999 %).
 However, for large node system, at almost any point
in time there’s a good chance that a node is either
down or there is a network disruption among the
nodes.
 Want a system that is resilient in the face of network
disruption

The CAP Theorem
A system can continue to
operate in the presence
of a network partitions.
Consistency
Partition
tolerance
Availability

The CAP Theorem
Theorem: You can have at
most two of these properties
for any shared-data system
Consistency
Partition
tolerance
Availability

What kinds of NoSQL
 NoSQL solutions fall into two major areas:
 Key/Value or ‘the big hash table’.
• Amazon S3 (Dynamo)
• Voldemort
• Scalaris
• Memcached (in-memory key/value store)
• Redis
 Schema-less which comes in multiple flavors, column-based,
document-based or graph-based.
• Cassandra (column-based)
• CouchDB (document-based)
• MongoDB(document-based)
• Neo4J (graph-based)
• HBase (column-based)

Key/Value
Pros:
 very fast
 very scalable
 simple model
 able to distribute horizontally
Cons:
- many data structures (objects) can't be easily modeled as key
value pairs

Schema-Less
Pros:
- Schema-less data model is richer than key/value pairs
- eventual consistency
- many are distributed
- still provide excellent performance and scalability
Cons:
- typically no ACID transactions or joins

Common Advantages
 Cheap, easy to implement (open source)
 Data are replicated to multiple nodes (therefore identical
and fault-tolerant) and can be partitioned
 Down nodes easily replaced
 No single point of failure
 Easy to distribute
 Don't require a schema
 Can scale up and down
 Relax the data consistency requirement (CAP)

What am I giving up?
 joins
 group by
 order by
 ACID transactions
 SQL as a sometimes frustrating but still powerful query
language
 easy integration with other applications that support SQL

Data Model
 A table in Bigtable is a sparse, distributed, persistent
multidimensional sorted map
 Map indexed by a row key, column key, and a timestamp
 (row:string, column:string, time:int64)  uninterpreted byte array
 Supports lookups, inserts, deletes
 Single row transactions only
Image Source: Chang et al., OSDI 2006

Rows and Columns
 Rows maintained in sorted lexicographic order
 Applications can exploit this property for efficient row scans
 Row ranges dynamically partitioned into tablets
 Columns grouped into column families
 Column key = family:qualifier
 Column families provide locality hints
 Unbounded number of columns

Bigtable Building Blocks
 GFS
 Chubby
 SSTable

SSTable
 Basic building block of Bigtable
 Persistent, ordered immutable map from keys to values
 Stored in GFS
 Sequence of blocks on disk plus an index for block lookup
 Can be completely mapped into memory
 Supported operations:
 Look up value associated with key
 Iterate key/value pairs within a key range
Index
64K
block
64K
block
64K
block
SSTable
Source: Graphic from slides by Erik Paulson

Tablet
 Dynamically partitioned range of rows
 Built from multiple SSTables
Index
64K
block
64K
block
64K
block
SSTable
Index
64K
block
64K
block
64K
block
SSTable
Tablet Start:aardvark End:apple

Table
 Multiple tablets make up the table
 SSTables can be shared
SSTable SSTable SSTable SSTable
Tablet
aardvark apple
Tablet
apple_two_E boat

Architecture
 Client library
 Single master server
 Tablet servers

Bigtable Master
 Assigns tablets to tablet servers
 Detects addition and expiration of tablet servers
 Balances tablet server load
 Handles garbage collection
 Handles schema changes

Bigtable Tablet Servers
 Each tablet server manages a set of tablets
 Typically between ten to a thousand tablets
 Each 100-200 MB by default
 Handles read and write requests to the tablets
 Splits tablets that have grown too large

Tablet Location
Upon discovery, clients cache tablet locations

Tablet Assignment
 Master keeps track of:
 Set of live tablet servers
 Assignment of tablets to tablet servers
 Unassigned tablets
 Each tablet is assigned to one tablet server at a time
 Tablet server maintains an exclusive lock on a file in Chubby
 Master monitors tablet servers and handles assignment
 Changes to tablet structure
 Table creation/deletion (master initiated)
 Tablet merging (master initiated)
 Tablet splitting (tablet server initiated)

Tablet Serving
“Log Structured Merge Trees”

Compactions
 Minor compaction
 Converts the memtable into an SSTable
 Reduces memory usage and log traffic on restart
 Merging compaction
 Reads the contents of a few SSTables and the memtable, and
writes out a new SSTable
 Reduces number of SSTables
 Major compaction
 Merging compaction that results in only one SSTable
 No deletion records, only live data

Bigtable Applications
 Data source and data sink for MapReduce
 Google’s web crawl
 Google Earth
 Google Analytics

Lessons Learned
 Fault tolerance is hard
 Don’t add functionality before understanding its use
 Single-row transactions appear to be sufficient
 Keep it simple!

HBase is an open-source,
distributed, column-oriented
database built on top of HDFS
based on BigTable!

HBase is ..
 A distributed data store that can scale
horizontally to 1,000s of commodity servers and
petabytes of indexed storage.
 Designed to operate on top of the Hadoop
distributed file system (HDFS) or Kosmos File
System (KFS, aka Cloudstore) for scalability,
fault tolerance, and high availability.

Benefits
 Distributed storage
 Table-like in data structure
 multi-dimensional map
 High scalability
 High availability
 High performance

Backdrop
 Started toward by Chad Walters and Jim
 2006.11
 Google releases paper on BigTable
 2007.2
 Initial HBase prototype created as Hadoop contrib.
 2007.10
 First useable HBase
 2008.1
 Hadoop become Apache top-level project and HBase becomes
subproject
 2008.10~
 HBase 0.18, 0.19 released

HBase Is Not …
 Tables have one primary index, the row key.
 No join operators.
 Scans and queries can select a subset of
available columns, perhaps by using a wildcard.
 There are three types of lookups:
 Fast lookup using row key and optional timestamp.
 Full table scan
 Range scan from region start to end.

HBase Is Not …(2)
 Limited atomicity and transaction support.
 HBase supports multiple batched mutations of single rows only.
 Data is unstructured and untyped.
 No accessed or manipulated via SQL.
 Programmatic access via Java, REST, or Thrift APIs.
 Scripting via JRuby.

Why Bigtable?
 Performance of RDBMS system is good for transaction
processing but for very large scale analytic processing, the
solutions are commercial, expensive, and specialized.
 Very large scale analytic processing
 Big queries – typically range or table scans.
 Big databases (100s of TB)

Why Bigtable? (2)
 Map reduce on Bigtable with optionally Cascading on top
to support some relational algebras may be a cost
effective solution.
 Sharding is not a solution to scale open source RDBMS
platforms
 Application specific
 Labor intensive (re)partitionaing

Why HBase ?
 HBase is a Bigtable clone.
 It is open source
 It has a good community and promise for the future
 It is developed on top of and has good integration for the
Hadoop platform, if you are using Hadoop already.
 It has a Cascading connector.

HBase benefits than RDBMS
 No real indexes
 Automatic partitioning
 Scale linearly and automatically with new nodes
 Commodity hardware
 Fault tolerance
 Batch processing

Data Model
 Tables are sorted by Row
 Table schema only define it’s column families .
 Each family consists of any number of columns
 Each column consists of any number of versions
 Columns only exist when inserted, NULLs are free.
 Columns within a family are sorted and stored together
 Everything except table names are byte[]
 (Row, Family: Column, Timestamp)  Value
Row key
Column Family
valueTimeStamp

Members
 Master
 Responsible for monitoring region servers
 Load balancing for regions
 Redirect client to correct region servers
 The current SPOF
 regionserver slaves
 Serving requests(Write/Read/Scan) of Client
 Send HeartBeat to Master
 Throughput and Region numbers are scalable by
region servers

ZooKeeper
 HBase depends on
ZooKeeper and by
default it manages a
ZooKeeper instance
as the authority on
cluster state

Operation
The -ROOT- table
holds the list
of .META. table
regions
The .META. table
holds the list of all
user-space
regions.

Installation (1)
$ wget
http://ftp.twaren.net/Unix/Web/apache/hadoop/hbase/hbase
-0.20.2/hbase-0.20.2.tar.gz
$ sudo tar -zxvf hbase-*.tar.gz -C /opt/
$ sudo ln -sf /opt/hbase-0.20.2 /opt/hbase
$ sudo chown -R $USER:$USER /opt/hbase
$ sudo mkdir /var/hadoop/
$ sudo chmod 777 /var/hadoop
START Hadoop…

Setup (1)
$ vim /opt/hbase/conf/hbase-env.sh
export JAVA_HOME=/usr/lib/jvm/java-6-sun
export HADOOP_CONF_DIR=/opt/hadoop/conf
export HBASE_HOME=/opt/hbase
export HBASE_LOG_DIR=/var/hadoop/hbase-logs
export HBASE_PID_DIR=/var/hadoop/hbase-pids
export HBASE_MANAGES_ZK=true
export
HBASE_CLASSPATH=$HBASE_CLASSPATH:/opt/hadoop/conf
$ cd /opt/hbase/conf
$ cp /opt/hadoop/conf/core-site.xml ./
$ cp /opt/hadoop/conf/hdfs-site.xml ./
$ cp /opt/hadoop/conf/mapred-site.xml ./

Setup (2)
<configuration>
<property>
<name> name </name>
<value> value </value>
</property>
</configuration>
Name value
hbase.rootdir hdfs://secuse.nchc.org.tw:9000/hb
ase
hbase.tmp.dir /var/hadoop/hbase-${user.name}
hbase.cluster.distribute
d
true
hbase.zookeeper.prop
erty.clientPort
2222
hbase.zookeeper.quor
um
Host1, Host2

Startup & Stop
$ start-hbase.sh
$ stop-hbase.sh

Testing (4)
$ hbase shell
> create 'test', 'data'
0 row(s) in 4.3066 seconds
> list
test
> put 'test', 'row1', 'data:1',
'value1'
'value2'
'value3'
> scan 'test'
ROW COLUMN+CELL
row1 column=data:1, timestamp=1240148026198,
value=value1
value=value2
value=value3
> disable 'test'
09/04/19 06:40:13 INFO client.HBaseAdmin: Disabled
test
> drop 'test'
09/04/19 06:40:17 INFO client.HBaseAdmin: Deleted
test
> list

Connecting to HBase
 Java client
 get(byte [] row, byte [] column, long timestamp, int
versions);
 Non-Java clients
 Thrift server hosting HBase client instance
 Sample ruby, c++, & java (via thrift) clients
 REST server hosts HBase client
 TableInput/OutputFormat for MapReduce
 HBase as MR source or sink
 HBase Shell
 JRuby IRB with “DSL” to add get, scan, and admin
 ./bin/hbase shell YOUR_SCRIPT

Thrift
 a software framework for scalable cross-language
services development.
 By facebook
 seamlessly between C++, Java, Python, PHP, and
Ruby.
 This will start the server instance, by default on port
9090
 The other similar project “rest”
$ hbase-daemon.sh start thrift
$ hbase-daemon.sh stop thrift

References
 Introduction to Hbase
trac.nchc.org.tw/cloud/raw-
attachment/wiki/.../hbase_intro.ppt

ACID
Atomic: Either the whole process of a transaction is done or
none is.
Consistency: Database constraints (application-specific) are
preserved.
Isolation: It appears to the user as if only one process executes
at a time. (Two concurrent transactions will not see on another’s
transaction while “in flight”.)
Durability: The updates made to the database in a committed
transaction will be visible to future transactions. (Effects of a
process do not get lost if the system crashes.)

CAP Theorem
Consistency: Every node in the system contains the
same data (e.g. replicas are never out of data)
Availability: Every request to a non-failing node in the
system returns a response
Partition Tolerance: System properties
(consistency and/or availability) hold even when the system
is partitioned (communicate lost) and data is lost (node lost)

Cassandra
Structured Storage System over a P2P
Network

Why Cassandra?
 Lots of data
 Copies of messages, reverse indices of messages, per user data.
 Many incoming requests resulting in a lot of random reads
and random writes.
 No existing production ready solutions in the market meet
these requirements.

Design Goals
 High availability
 Eventual consistency
 trade-off strong consistency in favor of high availability
 Incremental scalability
 Optimistic Replication
 “Knobs” to tune tradeoffs between consistency,
durability and latency
 Low total cost of ownership
 Minimal administration

innovation at scale
 google bigtable (2006)
 consistency model: strong
 data model: sparse map
 clones: hbase, hypertable
 amazon dynamo (2007)
 O(1) dht
 consistency model: client tune-able
 clones: riak, voldemort
cassandra ~= bigtable + dynamo

proven
 The Facebook stores 150TB of data on 150 nodes
web 2.0
 used at Twitter, Rackspace, Mahalo, Reddit, Cloudkick,
Cisco, Digg, SimpleGeo, Ooyala, OpenX, others

Data Model
KEY
ColumnFamily1 Name : MailList Type : Simple Sort : Name
Name : tid1
Value : <Binary>
TimeStamp : t1
Name : tid2
Value : <Binary>
TimeStamp : t2
Name : tid3
Value : <Binary>
TimeStamp : t3
Name : tid4
Value : <Binary>
TimeStamp : t4
ColumnFamily2 Name : WordList Type : Super Sort : Time
Name : aloha
ColumnFamily3 Name : System Type : Super Sort : Name
Name : hint1
<Column List>
Name : hint2
<Column List>
Name : hint3
<Column List>
Name : hint4
<Column List>
C1
V1
T1
C2
V2
T2
C3
V3
T3
C4
V4
T4
Name : dude
C2
V2
T2
C6
V6
T6
Column Families
are declared
upfront
Columns are
added and
modified
dynamically
SuperColumns
are added and
modified
dynamically
Columns are
added and
modified
dynamically

Write Operations
 A client issues a write request to a random node in the
Cassandra cluster.
 The “Partitioner” determines the nodes responsible for the
data.
 Locally, write operations are logged and then applied to an
in-memory version.
 Commit log is stored on a dedicated disk local to the
machine.

Write cont’d
Key (CF1 , CF2 , CF3)
Commit Log
Binary serialized
Key ( CF1 , CF2 , CF3 )
Memtable ( CF1)
Memtable ( CF2)
Memtable ( CF2)
• Data size
• Number of Objects
• Lifetime
Dedicated Disk
<Key name><Size of key Data><Index of columns/supercolumns><
Serialized column family>
---
---
---
---
<Key name><Size of key Data><Index of columns/supercolumns><
Serialized column family>
BLOCK Index <Key Name> Offset, <Key Name> Offset
K128 Offset
K256 Offset
K384 Offset
Bloom Filter
(Index in memory)
Data file on disk

Compactions
K1 < Serialized data >
--
--
--
Sorted
--
--
--
Sorted
--
--
--
Sorted
MERGE SORT
Sorted
K1 Offset
K5 Offset
K30 Offset
Bloom Filter
Loaded in memory
Index File
Data File
D E L E T E D

Write Properties
 No locks in the critical path
 Sequential disk access
 Behaves like a write back Cache
 Append support without read ahead
 Atomicity guarantee for a key
“Always Writable”
 accept writes during failure scenarios

Read
Query
Closest replica
Cassandra Cluster
Replica A
Result
Replica B Replica C
Digest Query
Digest Response Digest Response
Result
Client
Read repair if
digests differ

01
1/2
F
E
D
C
B
A N=3
h(key2)
h(key1)
93
Partitioning And Replication

Cluster Membership and Failure
Detection
 Gossip protocol is used for cluster membership.
 Super lightweight with mathematically provable properties.
 State disseminated in O(logN) rounds where N is the number of nodes
in the cluster.
 Every T seconds each member increments its heartbeat counter and
selects one other member to send its list to.
 A member merges the list with its own list .

Accrual Failure Detector
 Valuable for system management, replication, load balancing etc.
 Defined as a failure detector that outputs a value, PHI, associated with
each process.
 Also known as Adaptive Failure detectors - designed to adapt to
changing network conditions.
 The value output, PHI, represents a suspicion level.
 Applications set an appropriate threshold, trigger suspicions and
perform appropriate actions.
 In Cassandra the average time taken to detect a failure is 10-15
seconds with the PHI threshold set at 5.

Information Flow in the
Implementation

Performance Benchmark
 Loading of data - limited by network bandwidth.
 Read performance for Inbox Search in production:
Search Interactions Term Search
Min 7.69 ms 7.78 ms
Median 15.69 ms 18.27 ms
Average 26.13 ms 44.41 ms

MySQL Comparison
 MySQL > 50 GB Data
Writes Average : ~300 ms
Reads Average : ~350 ms
 Cassandra > 50 GB Data
Writes Average : 0.12 ms
Reads Average : 15 ms

Lessons Learnt
 Add fancy features only when absolutely required.
 Many types of failures are possible.
 Big systems need proper systems-level monitoring.
 Value simple designs

Future work
 Atomicity guarantees across multiple keys
 Analysis support via Map/Reduce
 Distributed transactions
 Compression support
 Granular security via ACL’s

Need for High-Level Languages
 Hadoop is great for large-data processing!
 But writing Java programs for everything is verbose and slow
 Not everyone wants to (or can) write Java code
 Solution: develop higher-level data processing languages
 Hive: HQL is like SQL
 Pig: Pig Latin is a bit like Perl

Hive and Pig
 Hive: data warehousing application in Hadoop
 Query language is HQL, variant of SQL
 Tables stored on HDFS as flat files
 Developed by Facebook, now open source
 Pig: large-scale data processing system
 Scripts are written in Pig Latin, a dataflow language
 Developed by Yahoo!, now open source
 Roughly 1/3 of all Yahoo! internal jobs
 Common idea:
 Provide higher-level language to facilitate large-data processing
 Higher-level language “compiles down” to Hadoop jobs

Hive: Background
 Started at Facebook
 Data was collected by nightly cron jobs into Oracle DB
 “ETL” via hand-coded python
 Grew from 10s of GBs (2006) to 1 TB/day new data
(2007), now 10x that
Source: cc-licensed slide by Cloudera

Hive Components
 Shell: allows interactive queries
 Driver: session handles, fetch, execute
 Compiler: parse, plan, optimize
 Execution engine: DAG of stages (MR, HDFS, metadata)
 Metastore: schema, location in HDFS, SerDe

Data Model
 Tables
 Typed columns (int, float, string, boolean)
 Also, list: map (for JSON-like data)
 Partitions
 For example, range-partition tables by date
 Buckets
 Hash partitions within ranges (useful for sampling, join
optimization)

Metastore
 Database: namespace containing a set of tables
 Holds table definitions (column types, physical layout)
 Holds partitioning information
 Can be stored in Derby, MySQL, and many other
relational databases

Physical Layout
 Warehouse directory in HDFS
 E.g., /user/hive/warehouse
 Tables stored in subdirectories of warehouse
 Partitions form subdirectories of tables
 Actual data stored in flat files
 Control char-delimited text, or SequenceFiles
 With custom SerDe, can use arbitrary format

Hive: Example
 Hive looks similar to an SQL database
 Relational join on two tables:
 Table of word counts from Shakespeare collection
 Table of word counts from the bible
Source: Material drawn from Cloudera training VM
SELECT s.word, s.freq, k.freq FROM shakespeare s
JOIN bible k ON (s.word = k.word) WHERE s.freq >= 1 AND k.freq >= 1
ORDER BY s.freq DESC LIMIT 10;
the 25848 62394
I 23031 8854
and 19671 38985
to 18038 13526
of 16700 34654
a 14170 8057
you 12702 2720
my 11297 4135
in 10797 12445
is 8882 6884

Hive: Behind the Scenes
SELECT s.word, s.freq, k.freq FROM shakespeare s
JOIN bible k ON (s.word = k.word) WHERE s.freq >= 1 AND k.freq >= 1
ORDER BY s.freq DESC LIMIT 10;
(TOK_QUERY (TOK_FROM (TOK_JOIN (TOK_TABREF shakespeare s) (TOK_TABREF bible k) (= (. (TOK_TABLE_OR_COL s)
word) (. (TOK_TABLE_OR_COL k) word)))) (TOK_INSERT (TOK_DESTINATION (TOK_DIR TOK_TMP_FILE)) (TOK_SELECT
(TOK_SELEXPR (. (TOK_TABLE_OR_COL s) word)) (TOK_SELEXPR (. (TOK_TABLE_OR_COL s) freq)) (TOK_SELEXPR (.
(TOK_TABLE_OR_COL k) freq))) (TOK_WHERE (AND (>= (. (TOK_TABLE_OR_COL s) freq) 1) (>= (. (TOK_TABLE_OR_COL k)
freq) 1))) (TOK_ORDERBY (TOK_TABSORTCOLNAMEDESC (. (TOK_TABLE_OR_COL s) freq))) (TOK_LIMIT 10)))
(one or more of MapReduce jobs)
(Abstract Syntax Tree)

Hive: Behind the Scenes
STAGE DEPENDENCIES:
Stage-1 is a root stage
Stage-2 depends on stages: Stage-1
Stage-0 is a root stage
STAGE PLANS:
Stage: Stage-1
Map Reduce
Alias -> Map Operator Tree:
s
TableScan
alias: s
Filter Operator
predicate:
expr: (freq >= 1)
type: boolean
Reduce Output Operator
key expressions:
expr: word
type: string
sort order: +
Map-reduce partition columns:
expr: word
type: string
tag: 0
value expressions:
expr: freq
type: int
expr: word
type: string
k
TableScan
alias: k
Filter Operator
predicate:
expr: (freq >= 1)
type: boolean
key expressions:
expr: word
type: string
sort order: +
Map-reduce partition columns:
expr: word
type: string
tag: 1
value expressions:
expr: freq
type: int
Reduce Operator Tree:
Join Operator
condition map:
Inner Join 0 to 1
condition expressions:
0 {VALUE._col0} {VALUE._col1}
1 {VALUE._col0}
outputColumnNames: _col0, _col1, _col2
Filter Operator
predicate:
expr: ((_col0 >= 1) and (_col2 >= 1))
type: boolean
Select Operator
expressions:
expr: _col1
type: string
expr: _col0
type: int
expr: _col2
type: int
outputColumnNames: _col0, _col1, _col2
File Output Operator
compressed: false
GlobalTableId: 0
table:
input format: org.apache.hadoop.mapred.SequenceFileInputFormat
output format: org.apache.hadoop.hive.ql.io.HiveSequenceFileOutputFormat
Stage: Stage-2
Map Reduce
Alias -> Map Operator Tree:
hdfs://localhost:8022/tmp/hive-training/364214370/10002
key expressions:
expr: _col1
type: int
sort order: -
tag: -1
value expressions:
expr: _col0
type: string
expr: _col1
type: int
expr: _col2
type: int
Reduce Operator Tree:
Extract
Limit
File Output Operator
compressed: false
GlobalTableId: 0
table:
input format: org.apache.hadoop.mapred.TextInputFormat
output format: org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat
Stage: Stage-0
Fetch Operator
limit: 10

Example Data Analysis Task
user url time
Amy www.cnn.com 8:00
Amy www.crap.com 8:05
Amy www.myblog.com 10:00
Amy www.flickr.com 10:05
Fred cnn.com/index.htm 12:00
url pagerank
www.cnn.com 0.9
www.flickr.com 0.9
www.myblog.com 0.7
www.crap.com 0.2
Find users who tend to visit “good” pages.
PagesVisits
...
...
Pig Slides adapted from Olston et al.

Conceptual Dataflow
Canonicalize URLs
Join
url = url
Group by user
Compute Average Pagerank
Filter
avgPR > 0.5
Load
Pages(url, pagerank)
Load
Visits(user, url, time)

System-Level Dataflow
. . . . . .
Visits Pages
...
... join by url
the answer
loadload
canonicalize
compute average pagerank
filter
group by user

MapReduce Code
import java.io.IOException;
import java.util.ArrayList;
import java.util.Iterator;
import java.util.List;
import org.apache.hadoop.fs.Path;
import org.apache.hadoop.io.LongWritable;
import org.apache.hadoop.io.Text;
import org.apache.hadoop.io.Writable;
import org.apache.hadoop.io.WritableComparable;
import org.apache.hadoop.mapred.FileInputFormat;
import org.apache.hadoop.mapred.FileOutputFormat;
import org.apache.hadoop.mapred.JobConf;
import org.apache.hadoop.mapred.KeyValueTextInputFormat;
import org.apache.hadoop.mapred.Mapper;
import org.apache.hadoop.mapred.MapReduceBase;
import org.apache.hadoop.mapred.OutputCollector;
import org.apache.hadoop.mapred.RecordReader;
import org.apache.hadoop.mapred.Reducer;
import org.apache.hadoop.mapred.Reporter;
import org.apache.hadoop.mapred.SequenceFileInputFormat;
import org.apache.hadoop.mapred.SequenceFileOutputFormat;
import org.apache.hadoop.mapred.TextInputFormat;
import org.apache.hadoop.mapred.jobcontrol.Job;
import org.apache.hadoop.mapred.jobcontrol.JobControl;
import org.apache.hadoop.mapred.lib.IdentityMapper;
public class MRExample {
public static class LoadPages extends MapReduceBase
implements Mapper<LongWritable, Text, Text, Text> {
public void map(LongWritable k, Text val,
OutputCollector<Text, Text> oc,
Reporter reporter) throws IOException {
// Pull the key out
String line = val.toString();
int firstComma = line.indexOf(',');
String key = line.substring(0, firstComma);
String value = line.substring(firstComma + 1);
Text outKey = new Text(key);
// Prepend an index to the value so we know which file
// it came from.
Text outVal = new Text("1" + value);
oc.collect(outKey, outVal);
}
}
public static class LoadAndFilterUsers extends MapReduceBase
implements Mapper<LongWritable, Text, Text, Text> {
public void map(LongWritable k, Text val,
// Pull the key out
String value = line.substring(firstComma + 1);
int age = Integer.parseInt(value);
if (age < 18 || age > 25) return;
String key = line.substring(0, firstComma);
// Prepend an index to the value so we know which file
// it came from.
Text outVal = new Text("2" + value);
oc.collect(outKey, outVal);
}
}
public static class Join extends MapReduceBase
implements Reducer<Text, Text, Text, Text> {
public void reduce(Text key,
Iterator<Text> iter,
// For each value, figure out which file it's from and
store it
// accordingly.
List<String> first = new ArrayList<String>();
List<String> second = new ArrayList<String>();
while (iter.hasNext()) {
Text t = iter.next();
String value = t.toString();
if (value.charAt(0) == '1')
first.add(value.substring(1));
else second.add(value.substring(1));
reporter.setStatus("OK");
}
// Do the cross product and collect the values
for (String s1 : first) {
for (String s2 : second) {
String outval = key + "," + s1 + "," + s2;
oc.collect(null, new Text(outval));
}
}
}
}
public static class LoadJoined extends MapReduceBase
implements Mapper<Text, Text, Text, LongWritable> {
public void map(
Text k,
Text val,
OutputCollector<Text, LongWritable> oc,
// Find the url
int secondComma = line.indexOf(',', firstComma);
String key = line.substring(firstComma, secondComma);
// drop the rest of the record, I don't need it anymore,
// just pass a 1 for the combiner/reducer to sum instead.
oc.collect(outKey, new LongWritable(1L));
}
}
public static class ReduceUrls extends MapReduceBase
implements Reducer<Text, LongWritable, WritableComparable,
Writable> {
public void reduce(
Text key,
Iterator<LongWritable> iter,
OutputCollector<WritableComparable, Writable> oc,
// Add up all the values we see
long sum = 0;
while (iter.hasNext()) {
sum += iter.next().get();
}
oc.collect(key, new LongWritable(sum));
}
}
public static class LoadClicks extends MapReduceBase
implements Mapper<WritableComparable, Writable, LongWritable,
Text> {
public void map(
WritableComparable key,
Writable val,
OutputCollector<LongWritable, Text> oc,
oc.collect((LongWritable)val, (Text)key);
}
}
public static class LimitClicks extends MapReduceBase
implements Reducer<LongWritable, Text, LongWritable, Text> {
int count = 0;
public void reduce(
LongWritable key,
Iterator<Text> iter,
OutputCollector<LongWritable, Text> oc,
// Only output the first 100 records
while (count < 100 && iter.hasNext()) {
oc.collect(key, iter.next());
count++;
}
}
}
public static void main(String[] args
JobConf lp = new JobConf(MRExampl
lp.setJobName("Load Pages");
lp.setInputFormat(TextInputFormat
lp.setOutputKeyClass(Text.class);
lp.setOutputValueClass(Text.class
lp.setMapperClass(LoadPages.class
FileInputFormat.addInputPath(lp,
Path("/user/gates/pages"));
FileOutputFormat.setOutputPath(lp
new Path("/user/gates/tmp/ind
lp.setNumReduceTasks(0);
Job loadPages = new Job(lp);
JobConf lfu = new JobConf(MRExamp
lfu.setJobName("Load and Filter U
lfu.setInputFormat(TextInputForma
lfu.setOutputKeyClass(Text.class)
lfu.setOutputValueClass(Text.clas
lfu.setMapperClass(LoadAndFilterU
FileInputFormat.addInputPath(lfu,
Path("/user/gates/users"));
FileOutputFormat.setOutputPath(lf
new Path("/user/gates/tmp/fil
lfu.setNumReduceTasks(0);
Job loadUsers = new Job(lfu);
JobConf join = new JobConf(MRExam
join.setJobName("Join Users and P
join.setInputFormat(KeyValueTextI
join.setOutputKeyClass(Text.class
join.setOutputValueClass(Text.cla
join.setMapperClass(IdentityMappe
join.setReducerClass(Join.class);
FileInputFormat.addInputPath(join
Path("/user/gates/tmp/indexed_pages"));
FileInputFormat.addInputPath(join
Path("/user/gates/tmp/filtered_users"));
FileOutputFormat.setOutputPath(jo
Path("/user/gates/tmp/joined"));
join.setNumReduceTasks(50);
Job joinJob = new Job(join);
joinJob.addDependingJob(loadPages
joinJob.addDependingJob(loadUsers
JobConf group = new JobConf(MRExa
group.setJobName("Group URLs");
group.setInputFormat(KeyValueText
group.setOutputKeyClass(Text.clas
group.setOutputValueClass(LongWri
group.setOutputFormat(SequenceFil
group.setMapperClass(LoadJoined.c
group.setCombinerClass(ReduceUrls
group.setReducerClass(ReduceUrls.
FileInputFormat.addInputPath(grou
Path("/user/gates/tmp/joined"));
FileOutputFormat.setOutputPath(gr
Path("/user/gates/tmp/grouped"));
group.setNumReduceTasks(50);
Job groupJob = new Job(group);
groupJob.addDependingJob(joinJob)
JobConf top100 = new JobConf(MREx
top100.setJobName("Top 100 sites"
top100.setInputFormat(SequenceFil
top100.setOutputKeyClass(LongWrit
top100.setOutputValueClass(Text.c
top100.setOutputFormat(SequenceFi
top100.setMapperClass(LoadClicks.
top100.setCombinerClass(LimitClic
top100.setReducerClass(LimitClick
FileInputFormat.addInputPath(top1
Path("/user/gates/tmp/grouped"));
FileOutputFormat.setOutputPath(to
Path("/user/gates/top100sitesforusers18to
top100.setNumReduceTasks(1);
Job limit = new Job(top100);
limit.addDependingJob(groupJob);
JobControl jc = new JobControl("F
18 to 25");
jc.addJob(loadPages);

Pig Latin Script
Visits = load ‘/data/visits’ as (user, url, time);
Visits = foreach Visits generate user, Canonicalize(url), time;
Pages = load ‘/data/pages’ as (url, pagerank);
VP = join Visits by url, Pages by url;
UserVisits = group VP by user;
UserPageranks = foreach UserVisits generate user,
AVG(VP.pagerank) as avgpr;
GoodUsers = filter UserPageranks by avgpr > ‘0.5’;
store GoodUsers into '/data/good_users';

Java vs. Pig Latin
0
20
40
60
80
100
120
140
160
180
Hadoop Pig
1/20 the lines of code
0
50
100
150
200
250
300
Hadoop Pig
Minutes
1/16 the development time
Performance on par with raw Hadoop!

Pig takes care of…
 Schema and type checking
 Translating into efficient physical dataflow
 (i.e., sequence of one or more MapReduce jobs)
 Exploiting data reduction opportunities
 (e.g., early partial aggregation via a combiner)
 Executing the system-level dataflow
 (i.e., running the MapReduce jobs)
 Tracking progress, errors, etc.

Integration
 Reasons to use Hive on HBase:
 A lot of data sitting in HBase due to its usage in a real-time
environment, but never used for analysis
 Give access to data in HBase usually only queried through
MapReduce to people that don’t code (business analysts)
 When needing a more flexible storage solution, so that rows can
be updated live by either a Hive job or an application and can be
seen immediately to the other
 Reasons not to do it:
 Run SQL queries on HBase to answer live user requests (it’s still a
MR job)
 Hoping to see interoperability with other SQL analytics systems

Integration
 How it works:
 Hive can use tables that already exist in HBase or manage its own
ones, but they still all reside in the same HBase instance
HBaseHive table definitions
Points to an existing table
Manages this table from Hive

Integration
 How it works:
 When using an already existing table, defined as EXTERNAL, you
can create multiple Hive tables that point to it
HBaseHive table definitions
Points to some column
Points to other
columns,
different names

Integration
 How it works:
 Columns are mapped however you want, changing names and giving
types
HBase tableHive table definition
name STRING
age INT
siblings MAP<string, string>
d:fullname
d:age
d:address
f:
persons people

Integration
 Drawbacks (that can be fixed with brain juice):
 Binary keys and values (like integers represented on 4 bytes)
aren’t supported since Hive prefers string representations, HIVE-
1634
 Compound row keys aren’t supported, there’s no way of using
multiple parts of a key as different “fields”
 This means that concatenated binary row keys are completely
unusable, which is what people often use for HBase
 Filters are done at Hive level instead of being pushed to the region
servers
 Partitions aren’t supported

Data Flows
 Data is being generated all over the place:
 Apache logs
 Application logs
 MySQL clusters
 HBase clusters

Data Flows
 Moving application log files
Wild log file
Read nightly
Transforms format
Dumped into
HDFS
Tail’ed
continuou
sly
Inserted into
HBaseParses into HBase format

Data Flows
 Moving MySQL data
MySQL
Dumped
nightly with
CSV import
HDFS
Tungsten
replicator
Inserted into
HBaseParses into HBase format

Data Flows
 Moving HBase data
HBase Prod
Imported in parallel into
HBase MRCopyTable MR job
Read in parallel
* HBase replication currently only works for a single slave cluster, in our case HBase
replicates to a backup cluster.

Use Cases
 Front-end engineers
 They need some statistics regarding their latest product
 Research engineers
 Ad-hoc queries on user data to validate some assumptions
 Generating statistics about recommendation quality
 Business analysts
 Statistics on growth and activity
 Effectiveness of advertiser campaigns
 Users’ behavior VS past activities to determine, for example, why
certain groups react better to email communications
 Ad-hoc queries on stumbling behaviors of slices of the user base

Use Cases
 Using a simple table in HBase:
CREATE EXTERNAL TABLE blocked_users(
userid INT,
blockee INT,
blocker INT,
created BIGINT)
STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler’
WITH SERDEPROPERTIES ("hbase.columns.mapping" =
":key,f:blockee,f:blocker,f:created")
TBLPROPERTIES("hbase.table.name" = "m2h_repl-
userdb.stumble.blocked_users");
HBase is a special case here, it has a unique row key map with
:key
Not all the columns in the table need to be mapped

Use Cases
 Using a complicated table in HBase:
CREATE EXTERNAL TABLE ratings_hbase(
userid INT,
created BIGINT,
urlid INT,
rating INT,
topic INT,
modified BIGINT)
STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler’
WITH SERDEPROPERTIES ("hbase.columns.mapping" =
":key#b@0,:key#b@1,:key#b@2,default:rating#b,default:topic#b,default:modified#b")
TBLPROPERTIES("hbase.table.name" = "ratings_by_userid");
#b means binary, @ means position in composite key (SU-specific hack)

NEO4J (Graphbase)
137
• A graph is a collection nodes (things) and edges (relationships) that connect
pairs of nodes.
• Attach properties (key-value pairs) on nodes and relationships
•Relationships connect two nodes and both nodes and relationships can hold an
arbitrary amount of key-value pairs.
• A graph database can be thought of as a key-value store, with full support for
relationships.
• http://neo4j.org/

NEO4J Features
144
• Dual license: open source and commercial
•Well suited for many web use cases such as tagging, metadata annotations,
social networks, wikis and other network-shaped or hierarchical data sets
• Intuitive graph-oriented model for data representation. Instead of static and
rigid tables, rows and columns, you work with a flexible graph network
consisting of nodes, relationships and properties.
• Neo4j offers performance improvements on the order of 1000x
or more compared to relational DBs.
• A disk-based, native storage manager completely optimized for storing
graph structures for maximum performance and scalability
• Massive scalability. Neo4j can handle graphs of several billion
nodes/relationships/properties on a single machine and can be sharded to
scale out across multiple machines
•Fully transactional like a real database
•Neo4j traverses depths of 1000 levels and beyond at millisecond speed.
(many orders of magnitude faster than relational systems)

Thank You
Presented by :
Rohit Dubey
8878695818
rohitdubey@live.com

HbaseHivePigbyRohitDubey

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to HbaseHivePigbyRohitDubey (20)

More from Rohit Dubey (16)

HbaseHivePigbyRohitDubey