This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Page tree
Skip to end of metadata
Go to start of metadata

This page describes how to build Impala from source and how to configure and run Impala in a single node development environment. 

Prerequisites and Requirements

Hardware Requirements

  • CPU must support at least SSSE3
  • Minimum memory: 16GB
  • Hard disk space: 120GB (for the test data)

Supported Operating Systems


  • Ubuntu 14.04, 16.04


Not supported


Not supported

Building Impala (for developing Impala)

  1. git clone ~/Impala
  2. cd ~/Impala
  3. export IMPALA_HOME=`pwd`
  4. $IMPALA_HOME/bin/

Building Impala without Test Data (for testing Impala)

  1. git clone ~/Impala
  2. cd ~/Impala
  3. export IMPALA_HOME=`pwd`
  4. $IMPALA_HOME/bin/
  5. source $IMPALA_HOME/bin/
  6. $IMPALA_HOME/ -noclean -notests
  7. $IMPALA_HOME/bin/ -create_metastore -create_sentry_policy_db
  8. $IMPALA_HOME/testdata/bin/
  9. $IMPALA_HOME/bin/

Installing and Configuring Impala (Obsolete)

  1. Install prerequisites

    Use to setup your Ubuntu 16.04 or Ubuntu 14.04 machine.
    By default, clones Impala in $HOME/Impala. To build Impala in a different directory, set IMPALA_HOME when running For example IMPALA_HOME=`pwd` ./

    If you are running on a platform that is not supported by the above script, you will have to install prerequisites and set up your machine manually. Impala Build Prerequisites has some information that can guide you.

  2. Clone the Impala git repo and change to the new Impala directory.

    git clone Impala
    cd Impala
  3. Set the following environment variables in your `.bashrc` or elsewhere:

    export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64
    export IMPALA_HOME=<path to Impala>
    export BOOST_LIBRARYDIR=/usr/lib/x86_64-linux-gnu
    export LC_ALL="en_US.UTF-8"
  4. Build Impala.

    # Build Impala and prepare the local mini-cluster (the first time only)
    ${IMPALA_HOME}/ -noclean -skiptests -format

    You may hit an error here in if you are building Impala on an operating system for which prebuilt toolchain binaries are not available. In that case you will need to build native-toolchain from scratch then retry this step.

    Want faster builds?

    Doing a full build of Impala can take quite a while! While you wait, check out Tips for Faster Impala Builds.

  5. Start supporting services.

    # This script starts or restarts the local services required for the test cluster
    # including HDFS, HBase, Hive and ZooKeeper. If you hit a problem with this script,
    # check the log files in ${IMPALA_HOME}/cluster_logs/ for clues.
    ${IMPALA_HOME}/ -noclean -notests -start_minicluster
  6. Start the Impala cluster.

    source ${IMPALA_HOME}/bin/ # You must source this in your shell before most of the below commands will work.
    # The following command will start an Impala cluster with 3 Impala demons, one 
    # Statestore and one Catalog demon.
  7. Check that everything works correctly.

    source ${IMPALA_HOME}/bin/ # If you didn't already source in this shell -q "SELECT version()"
    Starting Impala Shell without Kerberos authentication
    Connected to localhost:21000
    Server version: impalad version 2.2.0-INTERNAL DEBUG (build 47c90e004aecb928a37b926080098d30b96b4330)
    Query: select version()
    | version()                                                                             |
    | impalad version 2.2.0-INTERNAL DEBUG (build 47c90e004aecb928a37b926080098d30b96b4330) |
    | Built on Sun, Mar 22 15:22:57 PDT 2015                                                |
    Fetched 1 row(s) in 0.05s
  8. Have fun...
  9. Recompile and restart the Impala cluster for your changes to take effect. See Tips for Faster Impala Builds for tips on how to do incremental builds.

    # Rebuild both backend and frontend
    ${IMPALA_HOME}/ -skiptests -noclean
    source ${IMPALA_HOME}/bin/ # If you didn't already source in this shell
     # Optional: Rebuild the impala binary only
    make -j$IMPALA_BUILD_THREADS impalad
    # Optional: Build the Java-side frontend only
    # Restart the Impala cluster

  • No labels


  1. In my opinion this page is made obsolete by bin/ Any objection to deleting it?

    1. I think this is still somewhat useful in that it provides some additional explanation of what the build does and workflow after the first full build (it's not great for that, but better than nothing). I'd probably prefer to leave it until we can strip away the unnecessary stuff and make it better focused on steps after bootstrapping.