Liquibase-mongodb extension issue

hi @MikeOlivas
for us to move onto paid version , we first need to check if liquibase can be useful for our mongo app as well.
I am doing a poc for same.
using liquibase-mongodb extension.
Its able to establish connection and make an entry in databasechangelock table
but during update it fails iwth this error

Exception in thread “main” java.lang.AbstractMethodError: Receiver class liquibase.ext.mongodb.changelog.MongoHistoryService does not define or inherit an implementation of the resolved method ‘abstract boolean isDatabaseChecksumsCompatible()’ of interface liquibase.changelog.ChangeLogHistoryService.
at liquibase.command.core.AbstractUpdateCommandStep.isUpToDateFastCheck(AbstractUpdateCommandStep.java:194)
at liquibase.command.core.AbstractUpdateCommandStep.isUpToDate(AbstractUpdateCommandStep.java:249)
at liquibase.command.core.AbstractUpdateCommandStep.run(AbstractUpdateCommandStep.java:60)
at liquibase.command.CommandScope.execute(CommandScope.java:213)
at liquibase.Liquibase.lambda$update$0(Liquibase.java:223)
at liquibase.Scope.lambda$child$0(Scope.java:197)
at liquibase.Scope.child(Scope.java:206)
at liquibase.Scope.child(Scope.java:196)
at liquibase.Scope.child(Scope.java:175)
at liquibase.Liquibase.runInScope(Liquibase.java:1361)
at liquibase.Liquibase.update(Liquibase.java:215)
at liquibase.Liquibase.update(Liquibase.java:197)
at liquibase.Liquibase.update(Liquibase.java:183)
at liquibase.Liquibase.update(Liquibase.java:161)

can you or someone help here?

here are my dependencies:

org.liquibase liquibase-core 4.23.0
  <dependency>
    <groupId>org.liquibase.ext</groupId>
    <artifactId>liquibase-mongodb</artifactId>
    <version>4.21.0</version>
    <exclusions>
      <exclusion>
        <groupId>org.mongodb</groupId>
        <artifactId>mongo-java-driver</artifactId>
      </exclusion>
      <exclusion>
        <groupId>org.mongodb</groupId>
        <artifactId>mongodb-driver</artifactId>
      </exclusion>
    </exclusions>
  </dependency>

Hi @Pooja Yes there is a bug when using the latest version of liquibase (4.23.0) and Mongo Community extension.
It should be fixed in 4.24.0.
In the meantime, you can drop back to Liquibase 4.21.0 or use Liquibase 4.21.0 and the Liquibase Commercial MongoDB extension which fully supports using mongosh to apply changes to your MongoDB databases.