Cherry Pick

Description

A Comma separated list of migrations that MigrateDB should consider when migrating or repairing. Migrations are considered in the order that they are supplied, overriding the default ordering. Leave blank to consider all discovered migrations.

Each item in the list must either be a valid migration version (e.g 2.1) or a valid migration description ( e.g. create_table).

For example:

Create migrations V1__create_table1.sql, V2__create_table2.sql, and R__create_view.sql
Run migratedb migrate -cherryPick="1,create_view"

The schema history table now shows migration V1 and create_view as being successfully applied. However V2 has been skipped and is marked as ‘ignored’. V2__create_table2.sql can be cherry picked for deployment at a later time.

Usage

Command line

./migratedb -cherryPick="2.0" migrate

Configuration File

migratedb.cherryPick=2.0

Environment Variable

MIGRATEDB_CHERRY_PICK=2.0

API

MigrateDb.configure()
    .cherryPick("2.0")
    .load()

Use Cases

Deferred migration execution

Let’s say you have a project with 3 migrations:

V1__fastCreate1.sql
V2__slowInsert2.sql
V3__fastCreate3.sql

Migration V2 takes a tremendously large amount of time to execute so you decide executing it overnight would be better, but still need to execute migrations V1 and V3. Without cherryPick this would involve deleting V2 from disk and adding it back when needed which is a tedious and error prone task. Using cherryPick we can simply migrate V1 and V3 immediately:

migratedb migrate -cherryPick="1,3"

When it comes to migrating V2, we can utilise outOfOrder as follows:

migratedb migrate -outOfOrder="true"