- Support for Liquibase 4.9.1.
- PR #180: Added support for MariaDB Connector 3.x.
- Support for Liquibase 4.9.0.
- Support for Liquibase 4.8.0.
- PR #182: Added masking for slave password - andreiMambu
- #183: The parameter --slave-password is not masked in logs
- Support for Liquibase 4.7.1.
- Support for Liquibase 4.7.0.
- Support for Liquibase 4.6.2.
- #148: Support createIndex with specifying index prefix length
- Support for Liquibase 4.6.1.
- Support for Liquibase 4.5.0.
- Support for Liquibase 4.4.3.
- Support for Liquibase 4.4.2.
-
Support for Liquibase 4.4.1.
-
#122: Add docker image with liquibase, liquibase-percona and percona toolkit
-
Support for Liquibase 4.4.0.
-
PR #112: Fixing typos - Jasper Vandemalle
-
#106: MySQL connection times out after pt-online-schema-change run
-
#118: Use catalogName instead of schemaName
- Support for Liquibase 4.3.5.
- Support for Liquibase 4.3.4.
- Support for Liquibase 4.3.3.
- #60: Add support for MariaDB JConnector
- #85: liquibase-percona 4.3.1 is not reproducible anymore
- #88: Support for Liquibase 4.3.2
-
The maven coordinates have changed. This extension is now available like the other liquibase extensions in the group
org.liquibase.ext.In order to add this extension, use the following snippet:
<dependency> <groupId>org.liquibase.ext</groupId> <artifactId>liquibase-percona</artifactId> <version>4.3.1</version> </dependency> -
#66: Change maven coordinates to be org.liquibase.ext
-
#74: Update Liquibase to 4.3.0
-
Support for Liquibase 4.3.1
-
Alignment with existing release process
-
The minimum Java runtime version is now Java 1.8.
-
Liquibase 4+ is supported.
-
Support for older liquibase versions has been dropped.
-
The XML namespace for this extension is now "http://www.liquibase.org/xml/ns/dbchangelog-ext/liquibase-percona".
This only is affecting you, if you use the UsePercona flag.
There is now also a XSD schema available, if you want to validate your XML changeset: https://raw.githubusercontent.com/liquibase/liquibase-percona/liquibase-percona-2.0.0/src/main/resources/dbchangelog-ext-liquibase-percona.xsd
See the file test-changelog.xml for an example.
Note: Usage of the schema is optional. In order to use the custom flags provided by this extension, you only need to declare the namespace.
-
The checksum calculation for changes that used UsePercona flag changed. You might need to recreate the changelog entries for these changes with the clearCheckSums command. See #64 for the explanation.
-
Fixed #56: Support liquibase 4.x
-
Fixed #57: Support perconaOptions per change
-
Fixed #64: Different changeset checksums with and without liquibase-percona
-
Fixed #65: Make build reproducible
- Fixed #58: Update versions (liquibase, percona-toolkit, mysql)
- Fixed #35: Add support for AddPrimaryKeyChange
- Fixed #37: Using quotes for liquibase.percona.options doesn't always work
- Fixed #53: Update to support latest liquibase 3.10.1
- Fixed #54: Update mysql-connector-java to 8.0.20
- Fixed #55: Update percona toolkit to 3.2.0
The minimum Java runtime version is now Java 1.7.
The system property liquibase.percona.options uses now a default value of --alter-foreign-keys-method=auto --nocheck-unique-key-change.
These two options are not added by default anymore when pt-osc is executed. They are added
now via the additional options system property. In case you have overridden this system property, make sure, to add
these options as well, if you need them.
- Fixed #29: Allow to override --nocheck-unique-key-changes and --alter-foreign-keys-method=auto
- Fixed #30: Update liquibase
- Fixed #28: Strange behavior when liquibase.percona.defaultOn is false
- Fixed #26: Stack Overflow using defaultOn=false System Property
- PR #27: fix a typo - kennethinsnow
pt-online-schema-change is executed now with the option --nocheck-unique-key-change.
This enables to add unique indexes, but can cause data loss, since duplicated rows are ignored.
See Percona Toolkit Documentation
for more information.
The plugin is only compatible with version 3.0.12 or later of Percona Toolkit.
- Upgraded liquibase to 3.5.5
- Verified compatibility to liquibase 3.6.2
- Fixed #14: Rollback of foreign key constraint changing constraint names problem
- Fixed #15: Unique key constraint cannot be added
- Fixed #20: Support "UsePercona flag" in XML changelogs
- Fixed #22: Cross database bug
- Fixed #16: Failing test PerconaAddForeignKeyConstraintChangeTest
- Fixed #17: Include Percona Toolkit into integration test
- Fixed #18: Use spotbugs instead of findbugs
- Fixed #19: Upgrade liquibase to 3.5.4
- Fixed #21: Couldn't determine password: JdbcConnection is unsupported: dbcp.PoolingDataSource$PoolGuardConnectionWrapper
- Fixed #23: Add support for dbcp2
- Added new system property
liquibase.percona.pathto specify the path where Percona Toolkit is installed.
- Fixed #13: Use default liquibase.properties as fallback
- Fixed #12: Cannot run migrations with the percona extension on a Spring Boot app with embedded Tomcat
- Upgraded liquibase to 3.5.3
- Support for MySQL Connector 6.0.x in addition to 5.1.x.
- Fixed #7: Foreign key constraints of AddColumn is ignored
- Fixed #8: Support addForeignKeyConstraintChange, addUniqueConstraintChange
- Fixed #9: Support for enabling pt-online-schema-changes on a per-change basis
- Fixed #10: Build fails with java7: UnsupportedClassVersion when running DatabaseConnectionUtilTest.testGetPasswordMySQL_6
- PR #4: Allow passing additional command line options to pt-online-schema-change
- PR #5: Support afterColumn attribute
- Fixed #2: Adding indexes via pt-online-schema-change
- Fixed #3: Altering column data types via pt-online-schema-change
- Added configuration property "liquibase.percona.skipChanges"
- Upgraded liquibase to 3.4.2
- Fixed #1: Tables with foreign keys
- Initial version compatible with liquibase 3.3.0
- Initial version compatible with liquibase 3.2.0