Spring Boot Application Start-up error - Multiple Cassandra Keyspace configuration

[RmshVe]

Hi,

Multiple Cassandra keyspace configuration works well with Spring 2.7.*. However, after upgrading it to Spring Boot 3.0.0, the application fails to start. The error message states that there are 4 CqlSession beans instead of 1 and bean creation exception is thrown.

I've also followed the below link and the reference code given below. Both are not working.

https://tech.willhaben.at/spring-boot-3-2-x-application-using-cassandra-with-multiple-keyspaces-624f12b6dd48
https://github.com/willhaben/spring-data-with-multiple-keyspaces

Any thoughts on this?

[mp911de]

Care to post the full stack trace?

[RmshVe]

I will share it. (Building a demo app) Can you please clarify whether Spring 3 supports multiple keyspace configurations with auto-configuration enabled?

[mp911de]

Spring 3 supports multiple keyspace

Not sure what you're talking about. Spring 3 is long out of support. May I assume that you're referring to Spring Boot?

Generally, Spring Boot provides auto-config for resources, one-of-each-kind. This means, one SQL data source, one Mongo client, one Cassandra CqlSession. If you want to use multiple keyspaces, then it depends on your usage pattern. Using CqlSession directly requires you to qualify beans.

Using Cassandra via Spring Data allows you to use SessionFactory. There's a routing variant AbstractRoutingSessionFactory that supports e.g. ThreadLocal selection of backing sessions.

When using Cassandra 5, you can also use different CqlTemplate instances with a single session and set the CqlTemplate.keyspace to associate a specific keyspace with each executed statement.

[spring-projects-issues]

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

[RmshVe]

Yes. I was referring to Spring Boot 3. I went with the directly using CqlSession with the qualifying beans approach. This works for me. Thanks for the clarification.