After upgrading from Liquibase 4.26.0 to 4.31.0, Liquibase is automatically creating snapshots when running changesets. This significantly slows down the process:

[liquibase.ui] (main) INFO  Running Changeset: redacted
[liquibase.snapshot] (main) INFO  Creating snapshot
[liquibase.changelog] (main) INFO  Index REDACTED_I4 created
[liquibase.changelog] (main) INFO  ChangeSet redacted ran successfully in 1296ms
[liquibase.ui] (main) INFO  Running Changeset: redacted
[liquibase.snapshot] (main) INFO  Creating snapshot
[liquibase.changelog] (main) INFO  Index REDACTED_I5 created
[liquibase.changelog] (main) INFO  ChangeSet redacted ran successfully in 1289ms
[liquibase.ui] (main) INFO  Running Changeset: redacted
[liquibase.snapshot] (main) INFO  Creating snapshot

We are using Liquibase programmatically and calling it like this:

var resourceAccessor = new DirectoryResourceAccessor(pathToChangeLogFiles);
try (var liquibase = new Liquibase(changeLogFile, resourceAccessor, databaseConnection))
{
    Scope.enter(Map.of(Scope.Attr.ui.name(), new LoggerUIService()));
    liquibase.setShowSummaryOutput(UpdateSummaryOutputEnum.LOG);

    liquibase.update(contexts);
}

Why is this happening and how can this behavior be disabled? Thank you very much in advance!

After upgrading from Liquibase 4.26.0 to 4.31.0, Liquibase is automatically creating snapshots when running changesets. This significantly slows down the process:

[liquibase.ui] (main) INFO  Running Changeset: redacted
[liquibase.snapshot] (main) INFO  Creating snapshot
[liquibase.changelog] (main) INFO  Index REDACTED_I4 created
[liquibase.changelog] (main) INFO  ChangeSet redacted ran successfully in 1296ms
[liquibase.ui] (main) INFO  Running Changeset: redacted
[liquibase.snapshot] (main) INFO  Creating snapshot
[liquibase.changelog] (main) INFO  Index REDACTED_I5 created
[liquibase.changelog] (main) INFO  ChangeSet redacted ran successfully in 1289ms
[liquibase.ui] (main) INFO  Running Changeset: redacted
[liquibase.snapshot] (main) INFO  Creating snapshot

We are using Liquibase programmatically and calling it like this:

var resourceAccessor = new DirectoryResourceAccessor(pathToChangeLogFiles);
try (var liquibase = new Liquibase(changeLogFile, resourceAccessor, databaseConnection))
{
    Scope.enter(Map.of(Scope.Attr.ui.name(), new LoggerUIService()));
    liquibase.setShowSummaryOutput(UpdateSummaryOutputEnum.LOG);

    liquibase.update(contexts);
}

Why is this happening and how can this behavior be disabled? Thank you very much in advance!

• java
• liquibase

• maybe this one docs.liquibase.com/parameters/should-snapshot-data.html can help – Hendra Commented Feb 6 at 17:33
• @Hendra: Thanks. I'm not sure if this is applicable when not using the CLI. Also, we're using the update command, not the generate-changelog command. – Manuel K Commented Feb 6 at 21:04

1 Answer 1

I believe it is a bug. I have created a GitHub issue: https://github.com/liquibase/liquibase/issues/6711