What restrictions apply when using this extension?

[hiranchaudhuri1]

I created code as suggested and ran a very basic change on Couchbase community edition. Liquibase received an error from Couchbase stating the change is only supported by the enterprise edition:

com.couchbase.client.core.error.HttpStatusCodeException: Unexpected HTTP status 400 Bad Request {"completed":true,"coreId":"0x17ca642800000001","httpBody":"{\"errors\":{\"maxTTL\":\"Supported in enterprise edition only\"}}","httpStatus":400,"idempotent":false,"lastDispatchedFrom":"127.0.0.1:62189","lastDispatchedTo":"localhost:8091","requestId":5,"requestType":"CoreHttpRequest","retried":0,"service":{"method":"POST","path":"/pools/default/buckets/liquibaseServiceBucket/scopes/liquibaseServiceScope/collections","type":"mgmt"},"status":"INVALID_ARGS","timeoutMs":75000,"timings":{"dispatchMicros":2415,"totalDispatchMicros":2415,"totalMicros":3441}}

Unfortunately it is not clear to me what Liquibase tried to achieve that can only be supported in the enterprise edition of Couchbase. Via the databasechangelog I simply tried to create a bucket and two scopes.

When switching to an enterprise cluster I received another error, this time it looked like this:

liquibase.exception.CommandExecutionException: com.couchbase.client.core.error.DecodingFailureException: Deserialization of content into target class liquibase.ext.couchbase.changelog.CouchbaseChangeLog failed; encoded = {"author":"hiran.chaudhuri","checkSum":"9:d41d8cd98f00b204e9800998ecf8427e","comments":null,"context":{"contexts":[],"originalString":null},"dateExecuted":"2024.12.05 12:09:54","deploymentId":"3396993402","description":"empty","execType":"EXECUTED","fileName":"liquibase/DatabaseChangeLog.xml","id":"2024-12-05-1","labels":[],"liquibaseVersion":"4.22.0","orderExecuted":1,"tag":null}

This time it looks as if the client is not prepared for the response given by the Couchbase cluster.

In the stack trace I can see liquibase-core-4.22.0.jar, liquibase-couchbase-0.1.2-ER.jar and java-client-3.5.2.jar.

Question for me: Are these known limitations? Are these unexpected limitations? How can I address this behaviour?