You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the upgrade of liquibase from 4.19.0 to 4.19.1 all the changesets are executed multiple times when percona toolkit is used.
This shows up in the integration tests:
[INFO] Altering new table...
[INFO] (in cleanup) Error altering new table `testdb`.`_person_new`: DBD::mysql::db do failed: Duplicate key name 'emailIdx' [for Statement "ALTER TABLE `testdb`.`_person_new` ADD UNIQUE INDEX emailIdx (email(10))"] at /home/runner/work/liquibase-percona/liquibase-percona/target/percona-toolkit/percona-toolkit-3.5.1/bin/pt-online-schema-change line 9511.
[INFO]
[INFO] 2023-03-02T12:01:24 Dropping new table...
[INFO] 2023-03-02T12:01:24 Dropped new table OK.
[INFO] `testdb`.`person` was not altered.
[INFO] Error altering new table `testdb`.`_person_new`: DBD::mysql::db do failed: Duplicate key name 'emailIdx' [for Statement "ALTER TABLE `testdb`.`_person_new` ADD UNIQUE INDEX emailIdx (email(10))"] at /home/runner/work/liquibase-percona/liquibase-percona/target/percona-toolkit/percona-toolkit-3.5.1/bin/pt-online-schema-change line 9511.
[INFO]
This is the second run and the change has already been applied, so it can't be applied once more...
The change in liquibase that introduced this is liquibase/liquibase#3574 - for creating the log of the sql statements, the method generate of the statement is called. And that's when pt-osc is executed...
The text was updated successfully, but these errors were encountered:
adangel
changed the title
Changeset with pt-osc are executed multiple times (liquibase 4.19.1)
Changes with pt-osc are executed multiple times (liquibase 4.19.1)
Mar 2, 2023
…ement (#304)
* Refactor PTOnlineSchemaChangeStatement to be a ExecutablePreparedStatement
Fixes#303
* Avoid duplicated logging when percona toolkit can't be used
With the upgrade of liquibase from 4.19.0 to 4.19.1 all the changesets are executed multiple times when percona toolkit is used.
This shows up in the integration tests:
This is the second run and the change has already been applied, so it can't be applied once more...
The change in liquibase that introduced this is liquibase/liquibase#3574 - for creating the log of the sql statements, the method
generate
of the statement is called. And that's when pt-osc is executed...The text was updated successfully, but these errors were encountered: