Liquibase cassandra fails

[dinchand]

@maximevw Firstly Thanks for the release 4.10.2 which fixed my previous issue.

However I now encounter a new one . When I run it I now get

Unexpected error running Liquibase: line 1:53 no viable alternative at input '(' (... TABLE contacting.DATABASECHANGELOG (ID [VARCHAR](...) [Failed SQL: (0) CREATE TABLE contacting.DATABASECHANGELOG (ID VARCHAR(255) NOT NULL, AUTHOR VARCHAR(255) NOT NULL, FILENAME VARCHAR(255) NOT NULL, DATEEXECUTED datetime NOT NULL, ORDEREXECUTED INT NOT NULL, EXECTYPE VARCHAR(10) NOT NULL, MD5SUM VARCHAR(35), DESCRIPTION VARCHAR(255), COMMENTS VARCHAR(255), TAG VARCHAR(255), LIQUIBASE VARCHAR(20), CONTEXTS VARCHAR(255), LABELS VARCHAR(255), DEPLOYMENT_ID VARCHAR(10))]

I did read about the compliance mode and #25 . I am not sure if all liquibase users should use that compliance mode. I tried with that as well but no luck. Any pointers ?

[maximevw]

@dinchand, good news for the fix 😄

Liquibase compliance mode is strongly recommended to avoid some unexpected behaviours happening in some scenarios (for example, creating a table and populating it immediately after will fail without the Liquibase compliance mode).

Also, it seems you're trying to run classic Liquibase for SQL here because the query is not valid CQL (varchar(N) does not exist in CQL, explaining the parsing error). Are you using Liquibase Cassandra? Because, as you can see here in the Liquibase Cassandra code, the syntax of the query creating the table DATABASECHANGELOG is different.

An example of integration in a Spring application is available here: liquibase/liquibase-cassandra#212 (comment). Also, I already successfully ran the standard example provided in the Liquibase documentation as you could see in the issue #25.

I hope a new version of Liquibase Cassandra will be released soon with this JDBC wrapper (since changes have been merged in their main branch few weeks ago: liquibase/liquibase-cassandra#205)

[dinchand]

@maximevw Again thanks for the clear explanations and pointers. I was indeed missing the Liquibase Cassandra as dependency.

Also after you suggested I tried using the latest Liquibase Cassandra. And now I hit

[2023-11-01 17:02:30] SEVERE [liquibase.ext] Could not get keyspace from connection
java.lang.ClassCastException: com.datical.liquibase.ext.database.jvm.ProJdbcConnection cannot be cast to com.ing.data.cassandra.jdbc.CassandraConnection
        at liquibase.ext.cassandra.database.CassandraDatabase.getKeyspace(CassandraDatabase.java:114)
        at liquibase.ext.cassandra.database.CassandraDatabase.getDefaultCatalogName(CassandraDatabase.java:136)
        at liquibase.database.AbstractJdbcDatabase.getLiquibaseCatalogName(AbstractJdbcDatabase.java:710)
        at liquibase.ext.cassandra.lockservice.LockServiceCassandra.getChangeLogLockTableName(LockServiceCassandra.java:197)
        at liquibase.ext.cassandra.lockservice.LockServiceCassandra.isLocked(LockServiceCassandra.java:183)

Possibly because the the CassandraConnection is an implementation of java.sql.Connection but liquibase has its own interface.

[maximevw]

Hello @dinchand,

Indeed, the latest version of Liquibase Cassandra (4.24.0) still relies on Simba JDBC driver, that's certainly why you got this cast exception.

You currently have the following alternative:

• waiting for the next release of Liquibase Cassandra, which should use this JDBC driver (I don't know when it is planned, but I guess soon as they generally release a version each month more or less)
• if you can't wait, you will have to re-build yourself a version based on this driver (as explained in the previously mentioned references to the ˋliquibase-cassandraˋ project, there are really few changes to do that).

[maximevw]

Hello @dinchand,

An issue similar to yours (but not exactly the same) has been found in liquibase-cassandra 4.25.0: liquibase/liquibase-cassandra#242.
So, I'm surprised it worked with your locally managed instance, but I don't exactly know your use case (do you use Liquibase in command-line? with Java API? with Spring Boot?) ...

[dinchand]

@maximevw I run it command line.

2 things I notice. The new version of Liquibase Cassandra works for me for my lower environment. However if i see the logs at level FINE I do see the java.lang.ClassCastException but I still finishes with a successful execution. So I think the exception is not the cause.

Also on a higher environment it failed with the error below. I also tested locally with your fix for the java.lang.ClassCastException . This indeed fixed the logs and I do not see the exceptions anymore but the execution still fails with the same error. (FYI the Cassandra is managed by a separate team and hence I do not if there are any changes in configuration of a lower vs higher environment but I will check with my team)

[2023-11-20 23:22:46] FINE [liquibase.servicelocator] Loaded liquibase.sqlgenerator.SqlGenerator instance com.datical.liquibase.ext.storedlogic.trigger.change.RenameTriggerGenerator
[2023-11-20 23:22:46] FINE [liquibase.configuration] No configuration value for liquibase.sql.showSqlWarnings found
[2023-11-20 23:22:46] FINE [liquibase.configuration] Configuration liquibase.sql.showSqlWarnings is using the default value of true
[2023-11-20 23:22:48] INFO [liquibase.command] Command execution complete
[2023-11-20 23:22:48] SEVERE [liquibase.integration] Error executing SQL SELECT TABLE_NAME, KEYSPACE_NAME, COMMENT FROM system_schema.tables WHERE keyspace_name = 'null' AND TABLE_NAME = 'databasechangelog': com.datastax.oss.driver.api.core.NoNodeAvailableException: No node was available to execute the query
liquibase.exception.CommandExecutionException: liquibase.exception.UnexpectedLiquibaseException: liquibase.exception.DatabaseException: Error executing SQL SELECT TABLE_NAME, KEYSPACE_NAME, COMMENT FROM system_schema.tables WHERE keyspace_name = 'null' AND TABLE_NAME = 'databasechangelog': com.datastax.oss.driver.api.core.NoNodeAvailableException: No node was available to execute the query
\tat liquibase.command.CommandScope.execute(CommandScope.java:237)
\tat liquibase.integration.commandline.CommandRunner.call(CommandRunner.java:55)
\tat liquibase.integration.commandline.CommandRunner.call(CommandRunner.java:24)
\tat picocli.CommandLine.executeUserObject(CommandLine.java:2041)
\tat picocli.CommandLine.access$1500(CommandLine.java:148)
\tat picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
\tat picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
\tat picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
\tat picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
\tat picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
\tat picocli.CommandLine.execute(CommandLine.java:2170)
\tat liquibase.integration.commandline.LiquibaseCommandLine.lambda$execute$2(LiquibaseCommandLine.java:391)
\tat liquibase.Scope.child(Scope.java:193)
\tat liquibase.Scope.child(Scope.java:169)
\tat liquibase.integration.commandline.LiquibaseCommandLine.lambda$execute$3(LiquibaseCommandLine.java:366)
\tat liquibase.Scope.child(Scope.java:193)
\tat liquibase.Scope.child(Scope.java:169)
\tat liquibase.integration.commandline.LiquibaseCommandLine.execute(LiquibaseCommandLine.java:363)
\tat liquibase.integration.commandline.LiquibaseCommandLine.main(LiquibaseCommandLine.java:103)
\tat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
\tat sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
\tat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
\tat java.lang.reflect.Method.invoke(Method.java:498)
\tat liquibase.integration.commandline.LiquibaseLauncher.main(LiquibaseLauncher.java:116)
Caused by: liquibase.exception.UnexpectedLiquibaseException: liquibase.exception.DatabaseException: Error executing SQL SELECT TABLE_NAME, KEYSPACE_NAME, COMMENT FROM system_schema.tables WHERE keyspace_name = 'null' AND TABLE_NAME = 'databasechangelog': com.datastax.oss.driver.api.core.NoNodeAvailableException: No node was available to execute the query
\tat liquibase.changelog.StandardChangeLogHistoryService.init(StandardChangeLogHistoryService.java:114)
\tat liquibase.command.core.helpers.DatabaseChangelogCommandStep.checkLiquibaseTables(DatabaseChangelogCommandStep.java:141)
\tat liquibase.command.core.helpers.DatabaseChangelogCommandStep.run(DatabaseChangelogCommandStep.java:91)
\tat liquibase.command.CommandScope.execute(CommandScope.java:214)

I compared the logs with my lower environment and it has following lines.

[2023-11-20 23:28:56] FINE [liquibase.servicelocator] Loaded liquibase.sqlgenerator.SqlGenerator instance com.datical.liquibase.ext.storedlogic.trigger.change.RenameTriggerGenerator
[2023-11-20 23:28:56] WARNING [liquibase.ext] expecting exactly 1 table with name DATABASECHANGELOG, got 0
[2023-11-20 23:28:56] FINE [liquibase.executor] Create Database Change Log Table

[maximevw]

Thanks for your feedback @dinchand.

I remain surprised it worked successfully in your lower environment without the fix for ClassCastException... but maybe I miss a subtlety :) However, it's a good thing to know the fix makes disappear this exception.

I let you check with your team for the NoNodeAvailableException. Just few ideas of points to check: the parameter localdatacenter is missing or incorrect (if you use the default balancing policy), a SSL misconfiguration (for example, in higher environment a mutual authentication is maybe required), ...
Do not hesitate to let me know if you find something interesting.

[dinchand]

@maximevw I must admit I feel stupid writing this. But at least I know the cause of my issues thanks to your pointers again !

the parameter basic.load-balancing-policy.local-datacenter was indeed incorrect for me. The lower env has a different value and hence I was getting the error and that was also the issue for Cosmos btw. It works now for all, however for Cosmos I need the correct policies to make it work. Again thanks to you for your quick replies...

To me this is definitely an improvement but not blocking.

[maximevw]

Great news! You're welcome 😉