Allow application to start if cassandra is unavailable [DATACASS-210]

[spring-projects-issues]

Chad Jaros opened DATACASS-210 and commented

If cassandra is not available at boot time, CassandraCqlSessionFactoryBean.afterPropertiesSet() causes the application to exit before completing the startup process. It is desirable for my application to complete booting and allow the application to start and report specific errors.

This can be accomplished by making the factory beans operate lazily, retrying the connection on demand and storing the session object once a connection is successfully made

---

Affects: 1.2 GA (Fowler)

Issue Links:

• DATACASS-460 NoHostAvailable not caught at bean declaration, but only at initialization
  ("is duplicated by")

1 votes, 1 watchers

[christophstrobl]

With Spring Boot being the main entry point for configuration of the SessionFactoryFactoryBean via the CassandraDataAutoConfiguration we should provide means avoid eager initialization of a provided CqlSession bean.
Introducing Supplier based alternatives and switching to lazy evaluation would allow the context to start without actually establishing a connection as long as no schema actions need to be performed.