quantranhong1999 commented on PR #2780: URL: https://github.com/apache/james-project/pull/2780#issuecomment-3138329730
> The tables would exist already after a migration, wouldnt it be fair to think the compression option on the table would be migrated as well? Yes. I think it should the table should be migrated when upgrading to Cassandra 5.0. > The problem would only occur if we setup a new cassandra 4 cluster with the updated java driver version... but wouldnt we want just running cass 5 on a new setup right away? I am not sure the community would upgrade to Cassandra 5.0 soon. Then 4.19.1 driver would be a breaking change for existing 4.x Cassandra, for example, no? (Unless we remove the compaction options like your latest commit for example) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@james.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@james.apache.org For additional commands, e-mail: notifications-h...@james.apache.org
