Impala provides:

• Familiar SQL interface that data scientists and analysts already know.
• Ability to query high volumes of data (“big data”) in Apache Hadoop.
• Distributed queries in a cluster environment, for convenient scaling and to make use of cost-effective commodity hardware.
• Ability to share data files between different components with no copy or export/import step; for example, to write with Pig, transform with Hive and query with Impala. Impala can read from and write to Hive tables, enabling simple data interchange using Impala for analytics on Hive-produced data.
• Single system for big data processing and analytics, so customers can avoid costly modeling and ETL just for analytics.
  

  How Cloudera Impala Works with CDH

  The following graphic illustrates how Impala is positioned in the broader Cloudera environment:

  

  The Impala solution is composed of the following components:

  • Clients – Entities including Hue, ODBC clients, JDBC clients, and the Impala Shell can all interact with Impala. These interfaces are typically used to issue queries or complete administrative tasks such as connecting to Impala.
  • Hive Metastore – Stores information about the data available to Impala. For example, the metastore lets Impala know what databases are available and what the structure of those databases is. As you create, drop, and alter schema objects, load data into tables, and so on through Impala SQL statements, the relevant metadata changes are automatically broadcast to all Impala nodes by the dedicated catalog service introduced in Impala 1.2.
  • Cloudera Impala – This process, which runs on DataNodes, coordinates and executes queries. Each instance of Impala can receive, plan, and coordinate queries from Impala clients. Queries are distributed among Impala nodes, and these nodes then act as workers, executing parallel query fragments.
  • HBase and HDFS – Storage for data to be queried.

  Queries executed using Impala are handled as follows:

  1. User applications send SQL queries to Impala through ODBC or JDBC, which provide standardized querying interfaces. The user application may connect to any impalad in the cluster. This impaladbecomes the coordinator for the query.
  2. Impala parses the query and analyzes it to determine what tasks need to be performed by impaladinstances across the cluster. Execution is planned for optimal efficiency.
  3. Services such as HDFS and HBase are accessed by local impalad instances to provide data.
  4. Each impalad returns data to the coordinating impalad, which sends these results to the client.

  Primary Impala Features

  Impala provides support for:

  • Most common SQL-92 features of Hive Query Language (HiveQL) including SELECT, joins, and aggregate functions.
  • HDFS and HBase storage, including:
    • HDFS file formats: delimited text files, Parquet, Avro, SequenceFile, and RCFile.
    • Compression codecs: Snappy, GZIP, Deflate, BZIP.
  • Common data access interfaces including:
    • JDBC driver.
    • ODBC driver.
    • Hue Beeswax and the Cloudera Impala Query UI.
  • impala-shell command-line interface.
  • Kerberos authentication.