You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should consider upgrading to Cassandra Driver 4.0. The new driver entirely changes how we integrate with Cassandra as concepts like the Cluster abstraction are no longer present.
Part of this ticket is to investigate whether we are able to migrate to the new driver at all. The OSS driver does not support reactive execution and it comes with a new package structure that requires rebasing of the whole Spring Data Cassandra project onto the new driver structure
Issue Links:
DATACASS-709 Add support for programmatic DriverConfigLoader
("is depended on by")
DATACASS-710 Migrate to native ReactiveSession and ReactiveResultSet
("is depended on by")
DATACASS-708 Extend QueryOptions with serial consistency and execution profile
("is depended on by")
DATACASS-704 Add utility to initialize and cleanup the CQL keyspace
Upgrading to the Cassandra 4 driver comes with several breaking changes:
New package structure
Removal of the intermediate Cluster object
Query builder uses immutable objects
Areas of work
Major version bump to Spring Data for Apache Cassandra 3
Removal of CassandraCqlClusterFactoryBean and CassandraClusterFactoryBean.
Extend CassandraCqlSessionFactoryBean with properties from CassandraClusterFactoryBean and CassandraSessionFactoryBean.
Deprecate CassandraSessionFactoryBean in favor of CassandraCqlSessionFactoryBean.
Keyspace creation and removal will be migrated into CassandraCqlSessionFactoryBean.
Migration of connection-related properties to CassandraCqlSessionFactoryBean (was: CassandraClusterFactoryBean)
QueryBuilder API must work with immutable query objects
Going forward it would make sense to extract general script handling into ScriptUtils, DatabasePopulator and CqlSessionInitializer utilities.
The following unknowns need to be addressed:
Will reactive support get merged into the OSS driver? If not, then it doesn't make so much sense to have the breaking upgrade as we don't benefit from the driver right now
Mark Paluch opened DATACASS-656 and commented
We should consider upgrading to Cassandra Driver 4.0. The new driver entirely changes how we integrate with Cassandra as concepts like the
Cluster
abstraction are no longer present.Part of this ticket is to investigate whether we are able to migrate to the new driver at all. The OSS driver does not support reactive execution and it comes with a new package structure that requires rebasing of the whole Spring Data Cassandra project onto the new driver structure
Issue Links:
DATACASS-709 Add support for programmatic DriverConfigLoader
("is depended on by")
DATACASS-710 Migrate to native ReactiveSession and ReactiveResultSet
("is depended on by")
DATACASS-708 Extend QueryOptions with serial consistency and execution profile
("is depended on by")
DATACASS-704 Add utility to initialize and cleanup the CQL keyspace
DATACASS-705 Introduce SessionFactoryFactoryBean
DATACASS-703 Move Keyspace initialization from CassandraClusterFactoryBean to CassandraCqlSessionFactoryBean
DATACASS-655 Eliminate a vulnerability of DataStax Cassandra driver
("supersedes")
DATACASS-695 Force quote everywhere configuration needed
("supersedes")
Referenced from: pull request #167
1 votes, 5 watchers
The text was updated successfully, but these errors were encountered: