Introducing setContactPoints(Collection<InetSocketAddress> contactPoints) conflicts with XML-based configuration as Spring's BeanDefinition picks up the ContactPoints property in dependence of the reflection method order and attempts to convert localhost into Collection<InetSocketAddress>. That happens occasionally. Currently looking for a fix
Using an instance supplier and avoiding reflection does the trick to consistently use contact points as string when configuring the CQL Session using XML
spring-projects-issues commentedMay 19, 2020
Mark Paluch opened DATACASS-766 and commented
The new driver allows specifying a port per Cassandra node and we should reflect this possibility in
CqlSessionFactoryBean
Referenced from: pull request #178
The text was updated successfully, but these errors were encountered: