clickhouse-migrate 0.0.4

Migration library for Clickhouse

ClickHouse Migrate

Python library for creating and applying migrations in ClickHouse database.

Installation

Installation via PyPi:

pip install clickhouse-migrate

Usage

To use this tool it is required to create and provide a directory in which the migration files will be created, stored and from which they will be applied. clickhouse-migrate tool supports clustered ClickHouse setup and therefore it requires ALL clickhouse servers that are clustered as a database parameter.

Environment variables

Required parameters can be provided as environment variables

# Comma separated ClickHouse connection strings from one cluster
# Can be as a single connection string in case of standalone clickhouse instance

CLICKHOUSE_MIGRATE_DATABASES="clickhouse+native://<user>:<pass>@<host1>:<port>, ... ,clickhouse+native://<user>:<pass>@<host2>:<port>"
CLICKHOUSE_MIGRATE_DIRECTORY=<path to directory with migrations files>

Create migration file

One can create a new migration via calling clickhouse-migrate create_migration command.

Command parameters:

-n / --name <name of a new migration file> — this is a required parameter

-dir / --migration_dir — optional parameter for providing path to directory with migration files, default value ./migrations, can be replaced by CLICKHOUSE_MIGRATE_DIRECTORY environment variable

Example usage:

clickhouse-migrate create_migration -n test_migration -dir migrations

After calling the above-mentioned command a blank migration file YYYY-MM-DD-HH-mm-ss_<migration_name>.py will be created in the migrations directory which was defined in command line arguments.

The content of the created file will look like this

from clickhouse_migrate import Step

migrations = [Step(sql="")]

One should use Step dataclass to create migrations. Migrations would be applied in the same order that they are stated in the migrations list variable. All of listed changes in the migration list variable are by default applied to all databases listed in the *.ini config file, since usually changes are required for all replicated instances.

If an SQL query stated in the Step dataclass should not be executed for all DB replicas one may use Step(sql="<sql query>", replicated=False) statement.

This rule does not apply in case there is only one connection string in *.ini file.

Apply migrations

One can apply migrations created via clickhouse-migrate create_migration command by calling clickhouse-migrate migrate. This command will check for already applied migrations and will only apply new ones.

Command parameters:

-db / --databases — optional parameter for providing database connection strings, can be replaced by CLICKHOUSE_MIGRATE_DATABASES environment variable

-dir / --migration_dir — optional parameter for providing path to directory with migration files, can be replaced by CLICKHOUSE_MIGRATE_DIRECTORY environment variable

Example usage:

clickhouse-migrate migrate -dir /home/my_project/migrations -db clickhouse+native://default:@host1:9000/db -db clickhouse+native://default:@host2:9000/db

After calling this command all changes from migration files will be applied step-by-step. Changes are stored in clickhouse_migrate table.