Maxime Wiewiora

Hello @hfrs123 As announced in my message [here](https://github.com/liquibase/liquibase-contribute-site/pull/104#issuecomment-2435843689), a new version (4.14.0) of Cassandra JDBC wrapper is now available including the support of Amazon Keyspaces and SigV4 plugin. You can...

Hello @filipelautert Sure, I should be able to start working on that during the next days. I'll keep you informed as soon as a first draft is ready.

Hello @filipelautert As discussed, I submitted PR #303 to improve the compatibility with AWS Keyspaces. Maybe @pasarbia could help for testing of the fix (following the discussions in #289). I...

Hello @pasarbia, According to the provided logs, it seems that the table DATABASECHANGELOGLOCK is not created/available yet when the next query on it (`SELECT *`) is executed. It also explains...

Hello @pasarbia Thank you for your feedback! I found this interesting topic in AWS Keyspaces documentation about tables creation: https://docs.aws.amazon.com/keyspaces/latest/devguide/working-with-tables.html#tables-create It seems that, for AWS (i.e. only when the compatibility...

Hello @pasarbia, Following the last discussions, I suggested a fix for the issue related to the unavailability of the `databaseChangelogLock` table in AWS Keyspaces, on this branch: https://github.com/maximevw/liquibase-cassandra/tree/fix/issue-297-complement If it...

Thanks for testing @pasarbia! It seems it failed to access the `system_schema_mcs`, but I don't know why exactly, so I'll try to add more logs when this specific query fails...

Hello @pasarbia I updated my branch https://github.com/maximevw/liquibase-cassandra/tree/fix/issue-297-complement. There was (at least) a SQL syntax error in my query. I also added more logs in case of error to ease debugging.

Thank you for this new test @pasarbia! With the added logs, I better understand what happened: the "databasechangeloglock" table is not even present in the system_schema_mcs.tables table when the check...

@pasarbia, the difference between your query and the one performed in liquibase is the case of the table name. So, I think the fix will be to use lower case...