What support does Liquibase have for Google BigQuery?

Features

The Google BigQuery Secure extension supports all the features of Liquibase that are supported by BigQuery in Liquibase Open Source. In addition, Google BigQuery Secure lets you use Liquibase Secure features including:

• Policy Checks: automatically analyze your changelogs for desired format and behavior to increase deployment success rates and uphold security best practices

• Secrets Management: keep your authentication data secure by integrating with third-party secrets vaults

• Structured Logging: improve your database observability by easily reading Liquibase data in your favorite analytics tool

• Operation Reports: generate reports of operations you perform on your database

• Flow Files: create repeatable, portable, and platform-independent Liquibase workflows to run in any of your CI/CD tools

• DATABASECHANGELOGHISTORY table (DBCLH): record a history of all changes you make to the database, including changes that are not tracked by the DATABASECHANGELOG table (DBCL)

• Remote file access: centralize file management with AWS S3 to build a reusable repository of Liquibase files you can update and retrieve

• Targeted rollback: avoid collateral damage by specifying which changesets in your changelog to undo

• Stored Logic: capture stored logic objects like procedures, functions, packages, and triggers

Supported Change types

• addAutoIncrement

• addCheckConstraint

• addColumn

• addDefaultValue

• addForeignKeyConstraint

• addLookupTable

• addNotNullConstraint

• addPrimaryKey

• addUniqueConstraint

• alterSequence

• createFunction

• createIndex

• createPackage

• createPackageBody

• createProcedure

• createSequence

• createSynonym

• createTable

• createTrigger

• createView

• customChange

• delete

• disableCheckConstraint

• disableTrigger

• dropAllForeignKeyConstraints

• dropCheckConstraint

• dropColumn

• dropDefaultValue

• dropForeignKeyConstraint

• dropFunction

• dropIndex

• dropNotNullConstraint

• dropPackage

• dropPackageBody

• dropPrimaryKey

• dropProcedure

• dropSequence

• dropSynonym

• dropTable

• dropTrigger

• dropUniqueConstraint

• dropView

• enableCheckConstraint

• enableTrigger

• executeCommand

• insert

• loadData

• loadUpdateData

• markUnused

• mergeColumns

• modifyDataType

• modifySql

• renameColumn

• renameSequence

• renameTable

• renameTrigger

• renameView

• setColumnRemarks

• setTableRemarks

• sql

• sqlFile

• stop

• tagDatabase

• update

Supported commands

• Update Commands

• Rollback Commands

• Init Commands

• Change Tracking Commands

• Database Inspection Commands

• Utility Commands

• Flow Commands

• Policy Checks Commands

Verified database versions

Known limitations

DATABASECHANGELOG inconsistency after a crash

Liquibase batches all DBCL and DBCLH inserts in memory and writes them as a single bulk INSERT at the end of the command. If the JVM is hard-killed (SIGINT, SIGKILL or OOM) before the flush completes, physical tables may already exist in the database while the tracking tables show no record of those changesets. This is BigQuery-specific. Other databases use transactional writes and remain consistent on failure.

Workaround: See Google BigQuery troubleshooting for detection steps and recovery procedure.