Installation

    Official pre-built binaries are typically compiled for x86_64 and leverage SSE 4.2 instruction set, so unless otherwise stated usage of CPU that supports it becomes an additional system requirement. Here’s the command to check if current CPU has support for SSE 4.2:

    To run ClickHouse on processors that do not support SSE 4.2 or have AArch64 or PowerPC64LE architecture, you should build ClickHouse from sources with proper configuration adjustments.

    It is recommended to use official pre-compiled packages for Debian or Ubuntu. Run these commands to install packages:

    1. sudo apt-get install apt-transport-https ca-certificates dirmngr
    2. sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv E0C56BD4
    4. echo "deb https://repo.clickhouse.tech/deb/stable/ main/" | sudo tee \
    5.     /etc/apt/sources.list.d/clickhouse.list
    6. sudo apt-get update
    9. sudo service clickhouse-server start
    10. clickhouse-client

    If you want to use the most recent version, replace stable with testing (this is recommended for your testing environments).

    You can also download and install packages manually from .

    Packages

    • clickhouse-common-static — Installs ClickHouse compiled binary files.
    • clickhouse-server — Creates a symbolic link for clickhouse-server and installs the default server configuration.
    • clickhouse-client — Creates a symbolic link for clickhouse-client and other client-related tools. and installs client configuration files.
    • clickhouse-common-static-dbg — Installs ClickHouse compiled binary files with debug info.

    From RPM Packages

    It is recommended to use official pre-compiled rpm packages for CentOS, RedHat, and all other rpm-based Linux distributions.

    First, you need to add the official repository:

    1. sudo yum install yum-utils
    2. sudo rpm --import https://repo.clickhouse.tech/CLICKHOUSE-KEY.GPG
    3. sudo yum-config-manager --add-repo https://repo.clickhouse.tech/rpm/stable/x86_64

    If you want to use the most recent version, replace stable with testing (this is recommended for your testing environments). is sometimes also available.

    Then run these commands to install packages:

    1. sudo yum install clickhouse-server clickhouse-client

    You can also download and install packages manually from here.

    It is recommended to use official pre-compiled tgz archives for all Linux distributions, where installation of deb or rpm packages is not possible.

    For production environments, it’s recommended to use the latest stable-version. You can find its number on GitHub page with postfix -stable.

    From Docker Image

    To run ClickHouse inside Docker follow the guide on . Those images use official deb packages inside.

    For non-Linux operating systems and for AArch64 CPU arhitecture, ClickHouse builds are provided as a cross-compiled binary from the latest commit of the master branch (with a few hours delay).

    • macOS — curl -O 'https://builds.clickhouse.tech/master/macos/clickhouse' && chmod a+x ./clickhouse
    • — curl -O 'https://builds.clickhouse.tech/master/freebsd/clickhouse' && chmod a+x ./clickhouse
    • AArch64 — curl -O 'https://builds.clickhouse.tech/master/aarch64/clickhouse' && chmod a+x ./clickhouse

    After downloading, you can use the clickhouse client to connect to the server, or clickhouse local to process local data. To run clickhouse server, you have to additionally download and users configuration files from GitHub.

    These builds are not recommended for use in production environments because they are less thoroughly tested, but you can do so on your own risk. They also have only a subset of ClickHouse features available.

    From Sources

    To manually compile ClickHouse, follow the instructions for Linux or .

    You can compile packages and install them or use programs without installing packages. Also by building manually you can disable SSE 4.2 requirement or build for AArch64 CPUs.

    1.   Client: programs/clickhouse-client
    2.   Server: programs/clickhouse-server

    You’ll need to create a data and metadata folders and chown them for the desired user. Their paths can be changed in server config (src/programs/server/config.xml), by default they are:

    1.   /var/lib/clickhouse/data/default/

    On Gentoo, you can just use emerge clickhouse to install ClickHouse from sources.

    To start the server as a daemon, run:

    1. $ sudo service clickhouse-server start

    If you don’t have service command, run as

    If the server doesn’t start, check the configurations in the file .

    You can also manually launch the server from the console:

    1. $ clickhouse-server --config-file=/etc/clickhouse-server/config.xml

    In this case, the log will be printed to the console, which is convenient during development.
    If the configuration file is in the current directory, you don’t need to specify the --config-file parameter. By default, it uses ./config.xml.

    ClickHouse supports access restriction settings. They are located in the users.xml file (next to config.xml).
    By default, access is allowed from anywhere for the default user, without a password. See user/default/networks.
    For more information, see the section “Configuration Files”.

    After launching server, you can use the command-line client to connect to it:

    1. $ clickhouse-client

    By default, it connects to localhost:9000 on behalf of the user default without a password. It can also be used to connect to a remote server using --host argument.

    The terminal must use UTF-8 encoding.
    For more information, see the section .

    Example:

    1. $ ./clickhouse-client
    2. ClickHouse client version 0.0.18749.
    3. Connecting to localhost:9000.
    4. Connected to ClickHouse server version 0.0.18749.
    6. :) SELECT 1
    8. SELECT 1
    10. ┌─1─┐
    11. │ 1 │
    12. └───┘
    14. 1 rows in set. Elapsed: 0.003 sec.
    15. :)

    Congratulations, the system works!

    To continue experimenting, you can download one of the test data sets or go through tutorial.