A Liquibase extension adding support for Google Cloud Spanner. Include this in your application project to run Liquibase database migration scripts against a Google Cloud Spanner database.
Executing multiple small DDL statements on Cloud Spanner can take a very long time. This means that the standard recommendation to use as small changesets as possible with Liquibase is not always the best choice when working with Cloud Spanner. Instead, it is recommended to create changesets that group multiple DDL statements into one DDL batch. Use SQL change and batch the DDL using batch statements.
You can also create a single change set that contains multiple Liquibase changes (e.g. createTable)
and create these in a batch by adding a SQL command before and after the changes. See
create-multiple-tables.spanner.yaml for
an example.
- Requires Liquibase 4.25.1
- Requires Liquibase 4.25.0
- Requires Liquibase 4.24.0
- Requires Liquibase 4.23.2
- Requires Liquibase 4.23.1
- Requires Liquibase 4.23.0
- NOTE: Liquibase removed version 4.22.0. There will therefore be no release 4.22.0 for this library.
- Requires SnakeYAML 2.0 (fixes CVE-2022-1471)
- Requires Liquibase 4.21.1 (uses SnakeYAML 2.0 API)
- Requires Liquibase 4.21.0
- Requires Liquibase 4.20.0
- Requires Liquibase 4.19.1
- Requires Liquibase 4.19.0
- Requires Liquibase 4.18.0
- Updated Google Cloud dependencies to latest version (26.16.0)
- Requires Liquibase 4.17.2
- Requires Liquibase 4.17.1
- Updated Google Cloud dependencies to latest version (26.9.0)
- Fixed #159: NullPointerException caused by index
- Requires Liquibase 4.17.0
- Requires Liquibase 4.16.1
- Requires Liquibase 4.16.0
- Requires Liquibase 4.15.0
- Requires Liquibase 4.14.0
- Requires Liquibase 4.13.0
- Requires Liquibase 4.12.0
- Requires Liquibase 4.11.0
- #121 Added support for configured databasechangelog/lock table names. by @cbuschka in #122
- Requires Liquibase 4.10.0
- Requires Liquibase 4.10.0
- Requires Liquibase 4.9.1
- Requires Liquibase 4.9.0
- Requires Liquibase 4.8.0
- Requires Liquibase 4.7.1
- Requires Liquibase 4.7.0
- Requires Liquibase 4.6.2
- Requires Liquibase 4.6.1
- Fixes a bug where statements could be generated in the Spanner dialect when multiple different databases had been configured, and the Spanner library was included in the build. See also #102
- Requires Liquibase 4.5.0
- Adds support for
CREATE [OR REPLACE] VIEWandDROP VIEWstatements
- Requires Liquibase 4.4.3.
- The version of this library now mirrors the version number of the Liquibase version that it requires.
- Added sample for Spring Boot integration
- Bug fix (#94): loadData change did not escape single quotes correctly
- Extension is no longer beta.
- deps: update to jdbc driver version 2.0 and set user agent
- Bug fix (#83): Columns in the primary key were always generated as not nullable, even when they were marked as nullable.
- Bug fix (#78): INTERLEAVED table was generated as FOREIGN KEY in snapshots
- Bug fix (#75, #76, #77): Wrong type names were generated in snapshots
- Bug fix: Removed logback configuration from build.
- Bug fix: Fixed a potential
ClassNotFoundExceptionforcom.google.spanner.admin.database.v1.DatabaseAdminGrpc
- Initial beta release.
Install Liquibase Community CLI from here. Alternatively, there are many other ways to install (e.g. brew on Mac OS/X). These examples were run with Liquibase 4.2.0.
Once Liquibase is installed, use the latest release or build your own liquibase-spanner-SNAPSHOT-all.jar and copy it into the Liquibase lib directory.
You can create a Spanner instance in the GCP console or use an emulator (with JDBC). You will also need to create a database for Liquibase to use.
Spanner CLI is a convenient way to access Spanner. It can be installed from here.
Configure the connection in the file liquibase.properties:
url: jdbc:cloudspanner:/projects/<project>/instances/<instance>/databases/<database>
Using the Liquibase CLI the following ChangeLogs are examples of using Spanner. Review Liquibase best practices. In this example, changelog.yaml is used as the master changelog.
Run:
liquibase --changeLog example/changelog.yaml
| Example | Description |
|---|---|
| create-schema.yaml | Create schema, including interleaved tables, column options, and indexes |
| load-data-singers.yaml | Load data into Singers table from CSV |
| load-update-data-singers.yaml | Insert or update data in Singers table from CSV |
| add-lookup-table-singers-countries.yaml | Create countries table as a foreign key from Country field in Singers |
| modify-data-type-singers-lastname.yaml | Alter STRING datatype in Singers LastName column |
| insert.yaml | Insert rows into Singers table |
| delete.yaml | Delete rows from Singers |
| update.yaml | Update rows in Singers |
See the samples directory for specific integrations with other frameworks, such as Spring Boot.
The following Liquibase ChangeTypes are supported:
createTable, dropTable, addColumn, modifyDataType, addNotNullConstraint, dropColumn, createIndex, dropIndex, addForeignKeyConstraint, dropForeignKeyConstraint, dropAllForeignKeyConstraints, addLookupTable, createView, dropView
The following Liquibase ChangeTypes are not allowed with Cloud Spanner:
addAutoIncrement, addDefaultValue, addPrimaryKey, addUniqueConstraint, dropUniqueConstraint, createProcedure, createSequence, dropDefaultValue, dropNotNullConstraint, dropPrimaryKey, dropProcedure, dropSequence, renameColumn, renameSequence, renameTable, renameView, setColumnRemarks, setTableRemarks, alterSequence
The following data DML ChangeTypes are supported:
insert, update, loadData, loadUpdateData
Note:
- Column OPTIONS and table INTERLEAVE must be applied using modifySql.
- Instead of unique constraints use unique indexes.
See limitations.md for a full list of limitations and unsupported features.
Some Spanner specific SQL, such as INTERLEAVE'd tables or column OPTIONS, require using Liquibase's modifySql. See create-schema.yml for an example of doing this.
In order to limit the number of schema updates in a 7-day period, run Liquibase with small changeSets. Alternatively, use SQL change and batch the DDL using batch statements.
There are DML limits for the number of rows affected during DML. The recommendation is to use partitioned DML. Using Spanner JDBC driver this can be configured using the AUTOCOMMIT_DML_MODE.
This has been implemented in some of the changeSet types such as mergeColumns, but not in all changeSet types such as delete.
There are a number of features that Spanner does not have such as sequences and stored procedures. The Liquibase extension will throw an exception during analysis of the changeSet in most cases, but not all. For example, a DELETE without a WHERE clause will fail in Spanner but not in the Liquibase extension.
| Gradle target | Description |
|---|---|
| test | Run mock and Spanner emulator tests |
| build | Build extension and run above tests |
| integrationTest | Run Spanner in GCP tests |
| jibDocker | Build a local runnable docker container |
Testing requirements:
- Emulator requires testcontainers and its requirements installed.
- Spanner in GCP requires SPANNER_PROJECT and SPANNER_INSTANCE environment variables set to an active instance
- Spanner in GCP requires application default credentials set or GOOGLE_APPLICATION_CREDENTIALS environent set
There are two JARs built:
- build/libs/liquibase-spanner-VERSION.jar
- build/libs/liquibase-spanner-VERSION-all.jar
The first JAR is just the extension itself, while the second one includes all of the dependencies needed to run with Liquibase. Install the second one into the Liquibase lib directory.
For contributions please see contributing and our code of conduct.
If you have any questions, find a bug, or have a feature request please open an issue. Please note that this extension is not officially supported as part of the Cloud Spanner product.