Skip to main content

Cloudera Impala Review Sheet

There has been a lot of constant interest in Cloudera Impala, which enables real-time, interactive analytical queries of the data stored in HBase or HDFS.
Below is a review sheet for Cloudera Impala based on multiple sources. Feel free to document anything which you may know differently.

What’s there:

-          USP:
o       Low latency querying for HDFS
-          Business Use case:
o       Can be used for near real time operations
-          Key Components:
o       Daemon : impalad – low latency daemon running on each datanode (mutually exclusive of MapReduce)
o       StateStore: Impala StateStore – high throughput scheduler which stores state of daemon running on nodes, also provides subscription service, thrift mode, failure detection (also for HA)
o       Shell: Impala Shell - standard querying interface
-          Production Ready Version



What’s not there (in current release):

-          Resource Manager
-          User Defined Function support for Hive
-          Delay Scheduling
-          Manual query aborts
-          DDL Statements
-          Procedures, Scheduled jobs


What to expect (in current release):

-          SQL-92 features of Hive Query language
-          Low latency start and fetch
-          ODBC support, Command Line Interface for querying
-          Kerberos authentication
-          Possible lesser cost of ownership than licensed counterparts like Hadapt

What not to expect (in current release):

-          RDBMS speed in all operations
-          Trevni support which will bring in support for columnar binary storage and   more compression options
-          Lot of consistent documentation

When to expect new features:

-          Q1’2013 for a more stable version
-          More feature loaded version in CDH5

Which are the closest product match:

-          Google F1
-          RAD labs Sparrow BatchSampling

How to update yourself

-          Impala mailing list
-          Cloudera blog


Where to download:

-          Beta Release

-          Documentation
-          Code
selective snapshot below: 



update: 6 Dec 2012: Title of post changed based on review comments received to sound more technically correct. 

Comments

Popular posts from this blog

Data deduplication tactics with HDFS and MapReduce

As the amount of data continues to grow exponentially, there has been increased focus on stored data reduction methods. Data compression, single instance store and data deduplication are among the common techniques employed for stored data reduction.
Deduplication often refers to elimination of redundant subfiles (also known as chunks, blocks, or extents). Unlike compression, data is not changed and eliminates storage capacity for identical data. Data deduplication offers significant advantage in terms of reduction in storage, network bandwidth and promises increased scalability.
From a simplistic use case perspective, we can see application in removing duplicates in Call Detail Record (CDR) for a Telecom carrier. Similarly, we may apply the technique to optimize on network traffic carrying the same data packets.
Some of the common methods for data deduplication in storage architecture include hashing, binary comparison and delta differencing. In this post, we focus on how MapReduce and…

Low latency SQL querying on HBase

HBase has emerged as one of the most popular NoSQL database offering distributed, versioned, non-relational tables hosted on commodity hardware. However, with a large set of users coming from a relational SQL world, it made sense to bring the SQL back in this NoSQL. With Apache Phoenix, database professionals get a convenient way to query HBase through SQL in a fast and efficient manner. Continuing our discussion with James Taylor, the founder of Apache Phoenix, we focus on the functional aspects of Phoenix in this second part of interaction.
Although Apache Phoenix started off with distinct low latency advantage, have the other options like Hive/Impala (integrated with HBase) caught up in terms of performance?
No, these other tools such as Hive and Impala have not invested in improving performance against HBase data, so if anything, Phoenix's advantage has only gotten bigger as our performance improves.  See this link for comparison of Apache Phoenix with Apache Hive and Cloudera Im…

Pricing models for Hadoop products

A look at the various pricing models adopted by the vendors in the Hadoop ecosystem. While the pricing models are evolving in this rapid and dynamic market, listed below are some of the major variations utilized by companies in the sphere.
1) Per Node:Among the most common model, the node based pricing mechanism utilizes customized rules for determining pricing per node. This may be as straight forward as pricing per name node and data node or could have complex variants of pricing based on number of core processors utilized by the nodes in the cluster or per user license in case of applications.
2) Per TB:The data based pricing mechanism charges customer for license cost per TB of data. This model usually accounts non replicated data for computation of cost.
3) Subscription Support cost only:In this model, the vendor prefers to give away software for free but charges the customer for subscription support on a specified number of nodes. The support timings and level of support further …