Investigate SessionFactory.doInSession(…) and ReactiveSessionFactory.doInSession(…) [DATACASS-768]

[spring-projects-issues]

Mark Paluch opened DATACASS-768 and commented

Spring Data's approach uses a CqlSession per keyspace/tenant to achieve multi-tenancy. Keeping multiple sessions is considered an anti-pattern by the driver which should not be used.

A singleton session with keyspace routing capabilities would require the Cassandra V5 protocol as the new version allows association of keyspaces per statement.

The new protocol is not yet available so we should investigate whether we can switch to a callback-pattern to enclose Cassandra calls. Implementations of SessionFactory could go ahead and issue a setKeyspace call before and after the execution.

We also need to consider how this could work in an asynchronous scenario

---

No further details from DATACASS-768